Closed ekzyis closed 2 months ago
.github/pull_request_template.md (4)
`27-29`: The prompt for discussing backwards compatibility is clear and effectively addresses a crucial aspect of sustainable software development. --- `35-37`: The inclusion of a direct question about quality assurance and readiness for production deployment is a valuable addition, ensuring that changes are stable and ready for live environments. --- `39-41`: Asking specifically about mobile testing for frontend changes is crucial in today's mobile-first world, ensuring that all users have a consistent experience. --- `43-45`: Prompting for explicit mention of new environment variables is a good practice, aiding in configuration management and ensuring smooth operation across various environments.
Checklist looks like this now:
Checklist
Are your changes backwards compatible? Please answer below:
Did you QA this? Could we deploy this straight to production? Please answer below:
For frontend changes: Tested on mobile? Please answer below:
Did you introduce any new environment variables? If so, call them out explicitly here:
Summary by CodeRabbit