READY/IN DEVELOPMENT/HOLD
- are there any tests (passing is done by CI)
- review is done by @mention
- code follows conventions
- there is readme or documentation
- purpose of PR is clear
A few sentences describing the overall goals of the pull request's commits.
List related PRs against other branches:
branch | PR |
---|---|
other_pr_production | link |
other_pr_master | link |
- Tests
- Documentation
Notes regarding deployment the contained body of work. These should note any db migrations, etc.
Outline the steps to test or reproduce the PR here.
git pull --prune
git checkout <feature_branch>
bundle; script/server
List general components of the application that this PR will affect: