bito-code-review[bot] commented on PR #15578:
URL: https://github.com/apache/grails-core/pull/15578#issuecomment-4255730951

   <!-- Bito Reply -->
   Agreed, the license header in the PR template would appear in every PR 
description, which isn't ideal. Removing it keeps the template focused on the 
checklist and description sections.
   
   **.github/PULL_REQUEST_TEMPLATE.md**
   ```
   ## Description
   <!-- Describe your change and the problem it solves. Link to the related 
issue(s) if they exist. -->
   
   ## Contributor Checklist
   
   Please review the following checklist before submitting your pull request. 
Pull requests that do not meet these requirements may be closed without review.
   
   ### Issue and Scope
   
   - [ ] This PR is linked to an existing issue that has been **acknowledged or 
approved** by the project team.
         If no approved issue exists, please give background on why this change 
is necessary.  Tickets are preferred for release change log history.
   - [ ] This PR addresses the **complete scope** of the linked issue. Partial 
implementations or unfinished
         work should not be submitted for review.
   - [ ] This PR contains a **single, focused change**. Unrelated changes 
should be submitted as separate pull requests.
   - [ ] This PR targets the **correct branch** for the type of change:
       - **Patch release branches** (e.g., `7.0.x`): Bug fixes only. No new 
features or API changes.
       - **Minor release branches** (e.g., `7.1.x`): New features are welcome, 
but must avoid breaking existing APIs.
       - **Major release branches** (e.g., `8.0.x`): Reserved for major 
changes. Breaking API changes are permitted.
   
   ### Code Quality
   
   - [ ] I have **added or updated tests** that cover the changes introduced in 
this PR.
         All code contributions are expected to include appropriate test 
coverage.
   - [ ] I have verified that all existing tests pass by running `./gradlew 
build --rerun-tasks`.
   - [ ] My code follows the project's **code style** guidelines. I have run 
`./gradlew codeStyle` and resolved
         any violations. See [Code Style](../CONTRIBUTING.md#code-style) for 
details.
   - [ ] This PR does **not** include mass reformatting, style-only changes, or 
large-scale refactoring unless
         it was **explicitly approved** in the linked issue. Unsolicited 
reformatting will not be accepted.
   
   ### Licensing and Attribution
   
   - [ ] All contributed code is provided under the [Apache License 
2.0](https://www.apache.org/licenses/LICENSE-2.0),
         and new source files include the appropriate **Apache license header**.
   - [ ] I have the necessary rights to submit this contribution and confirm it 
is my own original work
         (see [Legal Notice](../CONTRIBUTING.md#i-want-to-contribute)).
   - [ ] If generative AI tooling was used in preparing this contribution, I 
have followed the
         [Apache Software Foundation's policy on generative 
tooling](https://www.apache.org/legal/generative-tooling.html)
         and have properly attributed its use.
   
   ### Documentation
   
   - [ ] If this PR introduces user-facing changes, I have included or updated 
the relevant documentation.
   - [ ] If this PR adds a new feature, I have updated the **What's New** 
section of the Grails Guide.
   - [ ] If this PR introduces breaking changes or changes that require user 
action during an upgrade, I have
         updated the **Upgrade Notes** for the corresponding version in the 
Grails Guide.
   - [ ] The PR description clearly explains **what** was changed and **why**.
   
   ---
   
   > **First-time contributors:** Please read our [Contributing 
Guide](../CONTRIBUTING.md) before submitting.
   > Pull requests that appear to be auto-generated, incomplete, or unrelated 
to an approved issue may be
   > closed to help maintainers focus on reviewed and planned work. We 
appreciate your understanding.
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to