3 ms·
I really don't think that having yet another process to skip the code review is the way to make it easier to use. Besides, the tooling won't support opposite wo
by user5994461 6y ago
I really don't think that having yet another process to skip the code review is the way to make it easier to use. Besides, the tooling won't support opposite workflows so this will have to be hacked in somehow (typical git commit hooks that randomly block commits with no explanation unless they have a magic word in the message).
If their team is small (less than 5 developers), don't make code review a hard blocker, there's never anybody available to code review.
- thawkins 6y agoPerhaps the company is growing, and has identified that the lack of code review on commits is creating quality issues.
- Smaug123 6y agoAgreed that it's worth OP diagnosing the actual source of friction here. My answer was implicitly predicated on the assumption of a largeish team, and I hadn't realised that.