Optimizing pull request for developer happiness

pullrequest github codereview

We as developers create a lot of pull requests from building new features to fixing bugs and typos.

When we create pull requests it is important to optimize for easy review by other developers and even by yourself at a later point in time. The goal of PR is to keep it simple, clutter-free and allow others to review without any cognitive overhead.

1. Provide clear context

2. Write code spec document if possible

3. Keep PR size small

4. Add Video / screenshots

5. Host the changes

6. Highlight critical changes

7. Don't squash the commits once the review has begun

8. Automate repeated checks

9. Don't get angry over a PR

Photo by Tim Mossholder on Unsplash

This post is also available on DEV.