You can follow best practices to improve the consistency and quality of pull requests and pull request reviews.

Pacifique Murangwa

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Best practices for creating and managing pull requests include writing small PRs, reviewing your own pull request first, providing context and guidance, using pull request templates, defining code owners, using protected branches, and using automated tools to review code styling.

Best practices for pull requests

Best practices for creating pull requests

Best practices for managing pull requests

I’d add here guiding the reviews by leaving comments on your own PRs. This is great for refactoring work where you move stuff between files.
As you review the PR from top to bottom you might not know at first where stuff was moved. So you’re inclined to scroll and try to find it, but that’ll just make the review slower.
I wrote about this tip here: <a href="https://akoskm.substack.com/p/how-to-make-your-code-changes-easier" target="_blank" rel="noopener nofollow">https://akoskm.substack.com/p/how-to-make-your-code-changes-easier</a>

Keep refactor changes away from functionality changes, different PRs if necessary