Pull Request - Do you do over the shoulder reviews?

Last updated by Brady Stroud [SSW] 3 months ago.See history

The PR author is responsible to follow up and get PRs merged as soon as possible. An "over-the-shoulder" review is one of the best ways to avoid merge debt.

When a pull request (PR) is ready to be reviewed, get someone with you either in-person or on call, and go through the PR together. This not only allows you to demo the content of the PR but also talk with the person taking feedback when needed.

When you have finished coding, don't just create a PR and throw it over the fence. Part of finishing a PR is getting it approved.
The best way to get it approved is via an "over the shoulder" review.

- Adam Cogan

Drafting PRs

A good way to avoid someone merging your PR before you have done an over the shoulder review is to keep the Pull Request in draft mode until you are ready for it to be reviewed for merging.

over the shoulder old PR
Figure: Bad example - Pressing commit and forgetting about it. PR has been left open for a over 2 weeks

over the shoulder pr
Figure: Good example - Devs reviewing a PR on a call - no merge debt!

We open source.Loving SSW Rules? Star us on GitHub. Star
Stand by... we're migrating this site to TinaCMS