Rules to Better Pull Requests

• Do you enable pull requests to ensure code is reviewed?
• Do you know how to write a great Pull Request (PR)?
• Pull Requests - Do you use and indicate Draft Pull Requests?
• Pull Request - Do you do over the shoulder reviews?
• Do you avoid Merge Debt?
• Do you use Pull Request templates to specify the expectations and requirements for each PR?
• Do you know to not 'Push' your Pull Requests? (aka discuss then build)
• Do you compare PR performance with Production before merging?
• Do you know when to add your changes to an existing PR?
• Do you include a useful description of your changes?
• Do you save failed experiments in abandoned pull requests?
• Do you use comments with @mentions to track changes in a PBI?
• Do you avoid linking issues to PRs in GitHub?
• Do you merge open source pull requests using the "Squash and merge" option?
• Do you have a standard set of pull request workflows?
• Do you still review Pull Requests when you are not a required viewer?
• Do you use Co-Creation Patterns?
• Do you use Co-Authored Commits?
• Do you have a page owner for each webpage?
• Do you have a clean git history?
• Do you know the best way to suggest changes on a Pull Request?
• Do you know how to indicate mandatory vs suggested PR changes?