Pre-merge Code Reviews
Rules, benefits, patterns, and anti-patterns for reviewing code before merging it.
about 1 year ago

I would probably add to the "Making it easier" checklist to use a linter that implements your team style guide so that you easily avoid "Focusing on junk details". You can also embed it in a test and add a git hook that does not allow to push if any test fails, it helps make the codebase consistent among the team ;)

about 1 year ago

👍 for the pre-push hook :)

Submit your answer