fix/contributing guide ai assistance (#2328)

* add contributors ai disclosure policy

* add disclosure and pr template

Author: motatoes

.github/pull_request_template.md

@@ -0,0 +1,25 @@
+### 🧠 AI Assistance Disclosure Policy
+
+> [!IMPORTANT]  
+> Inspired by [ghostty](https://github.com/ghostty-org/ghostty/blob/main/CONTRIBUTING.md#ai-assistance-notice).  
+> If you used **any AI assistance** while contributing to Digger, you must disclose it in this PR.
+
+---
+
+#### ✅ AI Disclosure Checklist
+
+- [ ] I understand that all AI assistance must be disclosed.
+- [ ] I did **not** use AI tools in this contribution.
+- [ ] I used AI tools and have disclosed details below.
+
+**Details (if applicable):**
+> _Example: Used ChatGPT to help with doc phrasing._  
+> _Example: Code generated by Copilot; reviewed and verified manually._
+
+---
+
+#### 💡 Notes
+
+- Trivial auto-completions (single words, short phrases) don’t need disclosure.
+- Contributors must understand and take responsibility for any AI-assisted code.
+- Failure to disclose is considered disrespectful to maintainers and may delay review.

CONTRIBUTING.md

@@ -23,6 +23,48 @@ and we would be happy to set you up.
 Digger is an open source terraform cloud alternative. We believe that open source software is important, and we welcome contributions from anyone who is interested in making our platform better.
 This document is intended to be a guide for people who want to contribute to Digger. We appreciate all contributions, no matter how big or small.
 
+## AI Assistance Notice
+
+> [!IMPORTANT]
+>
+> We have an AI assistance policy inspired by 
+> [ghostty](https://github.com/ghostty-org/ghostty/blob/main/CONTRIBUTING.md#ai-assistance-notice).
+> We copied the same policy with a few modifications below
+> If you are using **any kind of AI assistance** to contribute to Digger,
+> it must be disclosed in the pull request.
+
+If you are using any kind of AI assistance while contributing to Digger,
+**this must be disclosed in the pull request**, along with the extent to
+which AI assistance was used (e.g. docs only vs. code generation).
+If PR responses are being generated by an AI, disclose that as well.
+As a small exception, trivial tab-completion doesn't need to be disclosed,
+so long as it is limited to single keywords or short phrases.
+
+An example disclosure:
+
+> This PR was written primarily by Claude Code.
+
+Or a more detailed disclosure:
+
+> I consulted ChatGPT to understand the codebase but the solution
+> was fully authored manually by myself.
+
+Failure to disclose this is first and foremost rude to the human operators
+on the other end of the pull request, but it also makes it difficult to
+determine how much scrutiny to apply to the contribution.
+
+In a perfect world, AI assistance would produce equal or higher quality
+work than any human. That isn't the world we live in today, and in most cases
+it's generating slop. I say this despite being a fan of and using them
+successfully myself (with heavy supervision)!
+
+When using AI assistance, we expect contributors to understand the code
+that is produced and be able to answer critical questions about it. It
+isn't a maintainers job to review a PR so broken that it requires
+significant rework to be acceptable.
+
+Please be respectful to maintainers and disclose AI assistance.
+
 ## How to contribute
 
 **If you are considering using digger within your organisation