Skip to content

Commit 0c78aa7

Browse files
vinckrory-bot
authored andcommitted
fix: update CONTRIBUTING.md
GitOrigin-RevId: c40330cae452ab009c3a86892c0c2772d82ccfb8
1 parent 1cdb046 commit 0c78aa7

File tree

1 file changed

+46
-4
lines changed

1 file changed

+46
-4
lines changed

CONTRIBUTING.md

Lines changed: 46 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -136,10 +136,24 @@ to add your example or Ory-related project to the awesome-ory README.
136136

137137
## Contribute code
138138

139-
Unless you are fixing a known bug, we **strongly** recommend discussing it with
140-
the core team via a GitHub issue or [in our chat](https://www.ory.com/chat)
141-
before getting started to ensure your work is consistent with Ory Hydra's
142-
roadmap and architecture.
139+
**All code contributions require prior discussion and agreement with maintainers
140+
before opening a pull request.**
141+
142+
This applies to bug fixes, new features, and refactoring. Before writing code:
143+
144+
1. Open a [Discussion](https://github.com/ory/hydra/discussions/new/choose) or
145+
[Issue](https://github.com/ory/hydra/issues/new/choose) describing the
146+
problem and your proposed solution.
147+
2. Wait for maintainer feedback and explicit agreement on the implementation
148+
approach.
149+
3. Only then begin writing code.
150+
151+
Pull requests without prior discussion may be closed without review. This policy
152+
exists to protect your time and maintainer time.
153+
154+
"Drive-by" PRs, even well-intentioned ones, often conflict with the project
155+
roadmap, duplicate ongoing work, or introduce architectural inconsistencies. A
156+
quick conversation can help avoid these problems.
143157

144158
All contributions are made via pull requests. To make a pull request, you will
145159
need a GitHub account; if you are unclear on this process, see GitHub's
@@ -195,6 +209,34 @@ you should change the status to "Ready for review" and
195209

196210
Reviewers will approve the pull request once they are satisfied with the patch.
197211

212+
### AI-assisted contributions
213+
214+
AI can be a valuable aid for writing code, documentation, and tests. However, to
215+
maintain the quality and reliability of Ory Hydra, please follow these
216+
guidelines:
217+
218+
- When submitting a pull request or issue that involved AI assistance, mention
219+
the tools you used and the extent of their involvement. This helps reviewers
220+
understand the context of your contribution.
221+
222+
- Pull requests created with AI assistance should address an existing, accepted
223+
issue. If you have an idea for a new feature or improvement, please open a
224+
discussion or issue first to ensure alignment with the project's direction
225+
before investing time in implementation.
226+
227+
- You must use AI responsibly when writing code. All contributions must be
228+
tested and verified before submission. Unreviewed AI-generated code will not
229+
be accepted, and repeated submissions of this nature may result in restricted
230+
contribution privileges.
231+
232+
- When using AI to help draft issues, discussions, or documentation, review and
233+
edit the output before submitting. AI tends to be verbose. Trim unnecessary
234+
content and ensure your submission is clear and focused.
235+
236+
Contributors must use AI responsibly. These guidelines exist to ensure that
237+
every contribution meets the high standards our community expects, while still
238+
embracing the productivity benefits that AI tools can provide.
239+
198240
## Contribute documentation
199241

200242
Please provide documentation when changing, removing, or adding features. All

0 commit comments

Comments
 (0)