This repository has been archived by the owner on Jul 15, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will add a template to all PRs created in this repo. How it looks is shown below, you should do these steps:
This is a non-functional change, and should have no impact on your apps' functionality. It also probably does not need a version bump / changelog bump, as it does not need to be deployed and can just carry along w/ other changes. (this could technically be merged in on red - but that's up to you and your team)
Note This is for your benefit :). If this is too cumbersome, and not useful - you should change it! This is a suggested starting point for you, based off of things that sound good to people who aren't making pull requests against your repo every day. If you just need one box that says "Yes, this was code reviewed" - Then delete everything from the file, and add that! This is supposed to make things easier, and help you. Not make things harder!
Example of how this would look for every PR
Summary
{Include information about what is being done in this merge and why. This should be easy to read.}
PR - Merge Checklist:
Custom Repo Checklist:
Dependencies:
Risks:
{Risks that are associated with this merge. Things that it could possibly take down in production if released.}
{NOTE: There is always some sort of Risk, don't leave this section blank!}
Rollback:
{How do you roll this back if it fails?}