DEV Community

loading...

Discussion on: Git branching done right with Gitflow & improving code quality with code reviews

Collapse
nikola profile image
Nikola Brežnjak Author

Our team's policy is that no code is commited to master before it passes a code review.

A code review is not there to convey distrust but it's there to strengthen the codebase and keep the reviewer up to date with the changes. Sometimes you don't notice what someone else will, by looking at your code.

After we got used to this, everybody across multiple teams agrees this was (for us) a great thing to do.