Pull Request Template
π Description
π Related Issue
Fixes #
π― Type of Change
- π Bug fix (non-breaking change that fixes an issue)
- β¨ New feature (non-breaking change that adds functionality)
- π₯ Breaking change (fix or feature that would cause existing functionality to change)
- π Documentation update
- π¨ Code style update (formatting, renaming)
- β»οΈ Code refactoring (no functional changes)
- β‘ Performance improvement
- π Security fix
- π§ͺ Test addition/update
- π§ Configuration change
- π¦ Build process change
β Checklist
Before submitting this PR, please ensure:
- I have read the Contributing Guidelines
- My code follows the project's style guidelines
- I have performed a self-review of my code
- I have commented my code, particularly in hard-to-understand areas
- I have made corresponding changes to the documentation
- My changes generate no new warnings
- I have added tests that prove my fix/feature works
- All tests pass locally (
npm test,cargo test) - All linting checks pass (
npm run lint,cargo clippy) - I have updated the CHANGELOG.md (if applicable)
- I have checked for security vulnerabilities
π§ͺ Testing
How to Test
1.
2.
3.
Test Results
| Test Case | Expected | Actual | Status |
|---|---|---|---|
| β /β |
πΈ Screenshots
| Before | After |
|---|---|
π Additional Notes
π Deployment Notes
For Reviewers
Code Review Checklist
- Code changes are necessary
- Tests are adequate
- Documentation is updated
- Security considerations addressed
- Performance impact considered
- Follows project conventions
Review Comments
Reminder: Be kind, constructive, and specific in your feedback. We're all working together to make Linuxy better! π§