@@ -137,10 +137,24 @@ to add your example or Ory-related project to the awesome-ory README.
137137
138138## Contribute code
139139
140- Unless you are fixing a known bug, we ** strongly** recommend discussing it with
141- the core team via a GitHub issue or [ in our chat] ( https://www.ory.com/chat )
142- before getting started to ensure your work is consistent with Ory Ory Elements's
143- roadmap and architecture.
140+ ** All code contributions require prior discussion and agreement with maintainers
141+ before opening a pull request.**
142+
143+ This applies to bug fixes, new features, and refactoring. Before writing code:
144+
145+ 1 . Open a [ Discussion] ( https://github.com/ory/elements/discussions/new/choose )
146+ or [ Issue] ( https://github.com/ory/elements/issues/new/choose ) describing the
147+ problem and your proposed solution.
148+ 2 . Wait for maintainer feedback and explicit agreement on the implementation
149+ approach.
150+ 3 . Only then begin writing code.
151+
152+ Pull requests without prior discussion may be closed without review. This policy
153+ exists to protect your time and maintainer time.
154+
155+ "Drive-by" PRs, even well-intentioned ones, often conflict with the project
156+ roadmap, duplicate ongoing work, or introduce architectural inconsistencies. A
157+ quick conversation can help avoid these problems.
144158
145159All contributions are made via pull requests. To make a pull request, you will
146160need a GitHub account; if you are unclear on this process, see GitHub's
@@ -196,6 +210,34 @@ you should change the status to "Ready for review" and
196210
197211Reviewers will approve the pull request once they are satisfied with the patch.
198212
213+ ### AI-assisted contributions
214+
215+ AI can be a valuable aid for writing code, documentation, and tests. However, to
216+ maintain the quality and reliability of Ory Elements, please follow these
217+ guidelines:
218+
219+ - When submitting a pull request or issue that involved AI assistance, mention
220+ the tools you used and the extent of their involvement. This helps reviewers
221+ understand the context of your contribution.
222+
223+ - Pull requests created with AI assistance should address an existing, accepted
224+ issue. If you have an idea for a new feature or improvement, please open a
225+ discussion or issue first to ensure alignment with the project's direction
226+ before investing time in implementation.
227+
228+ - You must use AI responsibly when writing code. All contributions must be
229+ tested and verified before submission. Unreviewed AI-generated code will not
230+ be accepted, and repeated submissions of this nature may result in restricted
231+ contribution privileges.
232+
233+ - When using AI to help draft issues, discussions, or documentation, review and
234+ edit the output before submitting. AI tends to be verbose. Trim unnecessary
235+ content and ensure your submission is clear and focused.
236+
237+ Contributors must use AI responsibly. These guidelines exist to ensure that
238+ every contribution meets the high standards our community expects, while still
239+ embracing the productivity benefits that AI tools can provide.
240+
199241## Contribute documentation
200242
201243Please provide documentation when changing, removing, or adding features. All
0 commit comments