2.0 KiB
2.0 KiB
🎟️ Evercatch Ticket
Resolves: EC-XXX
🎯 Purpose & Impact
Please provide a clear, high-level summary of the change and its intended impact. Why is this change valuable to the Evercatch platform?
🛠️ Key Changes
📸 Screenshots or Videos
✅ Author's Definition of Done
- I have performed a self-review of my own code.
- My code follows the style guidelines and architectural patterns of this project.
- I have added or updated tests that prove my feature works or my fix is effective.
- All new and existing tests pass locally with my changes.
- I have made corresponding changes to the documentation (if applicable).
🔬 Reviewer's Guide & Additional Info (Click to Expand)
Where should the reviewer start?
🏷️ Type of Change
- FEAT: A new feature
- FIX: A bug fix
- DOCS: Documentation only changes
- STYLE: Code style changes (formatting, etc.)
- REFACTOR: A code change that neither fixes a bug nor adds a feature
- PERF: A code change that improves performance
- TEST: Adding missing tests or correcting existing tests
- CHORE: Changes to the build process or auxiliary tools