You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/about/contributing/AI_CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,17 +5,17 @@ It applies to all Coder repositories and is supplementary to the existing contri
5
5
6
6
For minor AI-assisted edits, suggestions, or completions where the human contributor is clearly the primary author, these rules do not apply — standard contributing guidelines are sufficient.
7
7
8
-
##Disclosure
8
+
###Disclosure
9
9
10
10
Contributors must**disclose AI involvement** in the pull request description whenever these guidelines apply.
11
11
12
-
##Human Ownership & Attribution
12
+
###Human Ownership & Attribution
13
13
14
14
- All pull requests must be opened under**real user accounts**.
15
15
- Contributors are personally accountable for the content of their PRs, regardless of how it was generated.
16
16
- Default to draft PRs until work has been tested and reviewed.
17
17
18
-
##Verification & Evidence
18
+
###Verification & Evidence
19
19
20
20
All AI-assisted contributions require**manual verification**.
21
21
Contributions without verification evidence will be rejected.
@@ -25,7 +25,7 @@ Contributions without verification evidence will be rejected.
25
25
- For visual/UI changes: include before/after screenshots.
26
26
- For CLI or backend changes: include terminal or api output.
27
27
28
-
#Why These Rules Exist
28
+
##Why These Rules Exist
29
29
30
30
Traditionally, maintainers assumed that producing a pull request required more effort than reviewing it.
31
31
With AI-assisted tools, the balance has shifted: generating code is often faster than reviewing it.