Files
lawnchair/.github/pull_request_template.md
2025-07-30 12:50:25 +08:00

42 lines
1.4 KiB
Markdown

<!--
Thanks for your contribution! A clear description and a test plan are the best way to get your PR reviewed and merged quickly.
For simple `Style` or `Chore` changes, a detailed description is optional.
-->
### Description
<!-- A clear and concise one-paragraph summary of what this PR does. -->
Fixes #(issue) <!-- optional -->
### Reasoning
<!--
(Optional - for major changes)
A more detailed explanation of the "why."
- Why was this change necessary? (e.g., technical debt, user feedback, architectural improvement)
- What are the core principles of the new solution?
-->
### Testing
<!--
(Optional - but highly encouraged for any functional change)
A step-by-step script for how to test these changes.
-->
### Type of change
<!-- Please replace the :x: with a :white_check_mark: for the ONE line that best describes your change. -->
:x: **Bug fix** (A non-breaking change that fixes an issue)
:x: **New feature** (A non-breaking change that adds functionality)
:x: **Breaking change** (A fix or feature that would cause existing functionality to not work as expected)
:x: **Refactor** (A code change that neither fixes a bug nor adds a feature)
:x: **Performance** (A code change that improves performance)
:x: **Style** (Code style changes)
:x: **Docs** (Changes to documentation)
:x: **Chore** (Changes to the build process or other tooling)