Handy/.github/PULL_REQUEST_TEMPLATE.md
Collin Stevens b710ff27c9
docs: add feature freeze notice to CONTRIBUTING.md and fix typo in PR template (#1175)
Add a visible feature freeze section near the top of CONTRIBUTING.md
so contributors see it before starting work. Fix "GATEHRED" typo in
the PR template.
2026-03-28 12:30:54 +08:00

71 lines
2.5 KiB
Markdown

## Before Submitting This PR
<!--
HANDY IS UNDERGOING A FEATURE FREEZE. IF YOU ARE SUBMITTING A PR WHICH IS A NEW FEATURE THAT THE COMMUNITY HAS NOT ASKED FOR: PREPARE TO BE REJECTED. IF THE COMMUNITY HAS ASKED FOR IT, OR YOU HAVE EXPLICITLY GATHERED SUPPORT IT MAY STILL BE CONSIDERED.
BUG FIXES ARE THE TOP PRIORITY. THERE ARE 60+ ISSUES TO FIX.
-->
**Please confirm you have done the following:**
- [ ] I have searched [existing issues](https://github.com/cjpais/Handy/issues) and [pull requests](https://github.com/cjpais/Handy/pulls) (including closed ones) to ensure this isn't a duplicate
- [ ] I have read [CONTRIBUTING.md](https://github.com/cjpais/Handy/blob/main/CONTRIBUTING.md)
**If this is a feature or change that was previously closed/rejected:**
- [ ] I have explained in the description below why this should be reconsidered
- [ ] I have gathered community feedback (link to discussion below)
## Human Written Description
<!-- Describe your changes clearly and concisely
Please write 2-3 sentences in your own words explaining:
- What problem you noticed or idea you had
- Why you think this change matters
This section should be YOUR thinking, not AI-generated text. Even if AI helped write the code, we want to hear from you directly. Your perspective as a human is what makes contributions meaningful. Your PR may be rejected if you do not
include a human-written description.
-->
## Related Issues/Discussions
<!-- Link to related issues, discussions, or previous PRs -->
<!-- If reopening something previously closed, explain why this should be reconsidered -->
Fixes #
Discussion:
## Community Feedback
<!--
PRs with community support are much more likely to be merged.
For features: Link to a discussion where community members have expressed interest.
For bug fixes: Link to the issue where others have confirmed the bug.
If you haven't gathered feedback yet, consider starting a discussion first:
https://github.com/cjpais/Handy/discussions
It is not explicitly required to gather feedback, but it certainly helps your PR get merged.
-->
## Testing
<!-- Describe how you tested your changes and if you need help getting additional testing -->
## Screenshots/Videos (if applicable)
<!-- Add screenshots or videos demonstrating the change -->
## AI Assistance
<!-- AI-assisted PRs are welcome! Just let us know so we can review appropriately. -->
- [ ] No AI was used in this PR
- [ ] AI was used (please describe below)
**If AI was used:**
- Tools used:
- How extensively: