[Improvement] Create hardened process to require MR approvals as a requirement before merge
Description
We need to enhance how we let code get merged into our main branches. We need to require reviews. There are other reasons to require reviews:
- Enable further collaboration between devs
- Encourage more communication between devs
- Enhance security by requiring this necessary step
- Enable further learning between devs by having us read each other’s code.
The Problem
Right now we don’t require reviews in a formal way. This can accidental lead to unwanted code being merged.
Background/Current State
Where are we now?
Solution
Document what the process is. How many approvals are required for a merge for non maintainers and how many for maintainers?
Additional Information
Steps
-
TBD