Depending on the size of your project, you probably have a variation on one of following types of review processes (or maybe a combination of several).
- Peer Review. We are all equals and equally able to review code and accept it to the project. We learn from one-another and do our best work when we know our peers will be judging it later.
- Automated Gatekeeper. Our code has test coverage. We trust our tests and only submit work we know will pass a comprehensive test suite. Typically we ask for a second opinion before the code is pushed into the test suite (for automated deployment).
- Consensus Shepherd. Our community of coders is vigilent, and opinionated. We require consensus from interested parties before code can be marked as "reviewed by the community". We may also have a testbot which is part of our community, making it easier for human coders to know when a suggested change meets minimum standards.
- Benevolent Dictator. My code, my way. You are welcome to submit your suggestions, but I will review, or have my lieutenants review, your work with a fine toothcomb. I enjoy finding your mistakes and rejecting your work. Only perfection is good enough.