(grails-core) branch contributingUpdates created (now 2f3d2e6485)

[jd...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jdaugherty pushed a change to branch contributingUpdates
in repository https://gitbox.apache.org/repos/asf/grails-core.git


      at 2f3d2e6485 #15386 - Update CONTRIBUTING.md to include guidelines for contributions using generative AI tooling

This branch includes the following new commits:

     new 2f3d2e6485 #15386 - Update CONTRIBUTING.md to include guidelines for contributions using generative AI tooling

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

(grails-core) 01/01: #15386 - Update CONTRIBUTING.md to include guidelines for contributions using generative AI tooling

[jd...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jdaugherty pushed a commit to branch contributingUpdates
in repository https://gitbox.apache.org/repos/asf/grails-core.git

commit 2f3d2e6485f1cdc0b2fc8de59a1a7ff896d8939f
Author: James Daugherty <jd...@jdresources.net>
AuthorDate: Wed Apr 22 08:33:36 2026 -0400

    #15386 - Update CONTRIBUTING.md to include guidelines for contributions using generative AI tooling
---
 CONTRIBUTING.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1fac494fb9..9bc19a8c21 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -39,6 +39,7 @@ All types of contributions are encouraged and valued. See the [Table of Contents
   - [Reporting Bugs](#reporting-bugs)
 - [Suggesting Enhancements](#suggesting-enhancements)
 - [Your First Code Contribution](#your-first-code-contribution)
+- [Contributions Using Generative AI Tooling](#contributions-using-generative-ai-tooling)
 - [Improving The Documentation](#improving-the-documentation)
 - [Code Style](#code-style)
 - [Commit Messages](#commit-messages)
@@ -191,6 +192,29 @@ Sometimes it's useful to debug your local application to see what's going wrong.
 
 By default, Grails forks a JVM to run the application. The `-debug-jvm` argument causes the debugger to be associated with the forked JVM.  You can then attach your debugger as proceed as normal.
 
+## Contributions Using Generative AI Tooling
+
+Contributions prepared with the help of generative AI tools are permitted, but the same quality, completeness, and attribution standards apply as for any other contribution. The submitter is fully responsible for the content of the pull request regardless of whether AI tooling was used.
+
+Before submitting an AI-assisted contribution:
+
+- **Comply with the [Apache Software Foundation's policy on generative tooling](https://www.apache.org/legal/generative-tooling.html).** Ensure that generated content is free of licensing or attribution issues and that you have the right to contribute it under the Apache License 2.0.
+- **Attribute AI usage.** Indicate in the pull request description if generative AI tooling was used and how, so reviewers have the context they need.
+- **Use a capable model.** Generated contributions must meet the project's quality bar. Low-effort output from weaker models that requires reviewers to finish the work is not acceptable.
+- **Read, understand, and verify the output.** Do not submit code, tests, or documentation that you have not reviewed yourself. You are accountable for every line.
+
+Pull requests prepared with AI tooling must also meet the following expectations — these are the most common reasons AI-assisted contributions are rejected:
+
+- **Linked to an approved issue.** The PR must reference an existing issue that has been acknowledged or approved by the project team. Speculative or unsolicited AI-generated work without an approved issue will be closed.
+- **Complete scope.** The PR must fully address the linked issue. Partial implementations, scaffolding without working behavior, or "starter" PRs expecting maintainers to finish the work will be closed.
+- **Focused change.** Submit a single, focused change per PR. Do not include unrelated refactors, mass reformatting, or style-only churn generated as a side effect of the AI's output.
+- **Tests included.** Behavior introduced or modified must be covered by new or updated tests that exercise the change through public APIs. See [Testing Your Change](#testing-your-change).
+- **Documentation included.** User-facing changes must include matching updates to the Grails Guide, including the *What's New* and *Upgrade Notes* sections where applicable. See [Improving The Documentation](#improving-the-documentation).
+- **Code style compliance.** Run `./gradlew codeStyle` locally and resolve violations before opening the PR.
+- **Targets the correct branch.** Respect the branch policy (patch branches accept bug fixes only; minor branches accept features without breaking APIs; major branches accept breaking changes). See the [Pull Request Template](.github/PULL_REQUEST_TEMPLATE.md) for details.
+
+Pull requests that appear to be auto-generated, incomplete, unrelated to an approved issue, or otherwise inconsistent with the project's standards may be closed without review so maintainers can focus on reviewed and planned work. See the [Pull Request Template](.github/PULL_REQUEST_TEMPLATE.md) for the full contributor checklist.
+
 ### Improving The Documentation
 
 There are many aspects to [Grail's documentation](https://grails.apache.org/docs/)