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: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,8 +32,8 @@ On [GitHub Codespaces](https://github.com/features/codespaces) it's even simpler
32
32
33
33
## Submitting a pull request
34
34
35
-
>[!NOTE]
36
-
>If your pull request introduces a large change that materially impacts the work of the CLI or the rest of the repository (e.g., you're introducing new templates, arguments, or otherwise major changes), make sure that it was **discussed and agreed upon** by the project maintainers. Pull requests with large changes that did not have a prior conversation and agreement will be closed.
35
+
>[!NOTE]
36
+
>If your pull request introduces a large change that materially impacts the work of the CLI or the rest of the repository (e.g., you're introducing new templates, arguments, or otherwise major changes), make sure that it was **discussed and agreed upon** by the project maintainers. Pull requests with large changes that did not have a prior conversation and agreement will be closed.
37
37
38
38
1. Fork and clone the repository
39
39
1. Configure and install the dependencies: `uv sync`
@@ -122,7 +122,7 @@ When submitting AI-assisted contributions, please ensure they include:
122
122
123
123
-**Clear disclosure of AI use** - You are transparent about AI use and degree to which you're using it for the contribution
124
124
-**Human understanding and testing** - You've personally tested the changes and understand what they do
125
-
-**Clear rationale** - You can explain why the change is needed and how it fits within Spec Kit's goals
125
+
-**Clear rationale** - You can explain why the change is needed and how it fits within Spec Kit's goals
126
126
-**Concrete evidence** - Include test cases, scenarios, or examples that demonstrate the improvement
127
127
-**Your own analysis** - Share your thoughts on the end-to-end developer experience
0 commit comments