-
Notifications
You must be signed in to change notification settings - Fork 19
PR template revamp v1.0
[Insert a brief, descriptive title for the pull request]
[Provide a detailed description of the changes made in the pull request, including any new features or bug fixes, and the rationale behind those changes]
[Identify the issue(s) that this pull request resolves. Use keywords such as "Closes," "Fixes," or "Resolves" followed by the issue number(s). For example, "Closes #123."]
[Provide screenshots or screen recordings (if applicable) of the changes made in the pull request]
[Provide a brief list of instructions on how to test the changes made in this pull request. This should be clear and concise, and it should not require a significant amount of time or effort to complete.]
[Outline the acceptance criteria that this pull request must meet in order to be approved and merged. Make sure that the criteria are clear, specific, and verifiable.]
[Identify any ethical considerations associated with the changes made in this pull request. This may include issues related to data privacy, bias, or other ethical concerns. Describe the steps that have been taken to address these concerns.]
Checklist:
- All acceptance criteria are met
- Code has been reviewed by at least one team member
- Code has been tested thoroughly and no new issues have been introduced
- Documentation has been updated (if applicable)
- Any necessary configuration changes have been made
- Changes have been merged into the appropriate branch
- Changes have been deployed to the appropriate environment (if applicable)