What: [One sentence describing what this PR does] Why: [One sentence explaining why this change is needed] Impact: [Who/what benefits from this 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 refactor/cleanup
- Performance improvement
- Testing improvements
Fixes #(issue number)
- Unit tests added/updated
- Manual testing performed
- Tested on different browsers/devices (if applicable)
- Edge cases considered and tested
- My code follows the project's style guidelines
- I have performed a self-review of my own code
- I have commented my code, particularly in hard-to-understand areas
- My changes generate no new warnings or errors
- I have added tests that prove my fix is effective or that my feature works
- New and existing unit tests pass locally with my changes
- Any dependent changes have been merged and published
- README updated (if needed)
- Code comments added/updated
- API documentation updated (if applicable)
- No documentation changes needed
Remember: Every PR is a learning opportunity. Don't worry about asking questions or requesting help. Excellence in All We Do!