> No PR, no code review, no CI. Just a cowboy pushing to the master.. Let's be clear that the dangers here are "no code review" and "no CI". The others are fi

> No PR, no code review, no CI. Just a cowboy pushing to the master.. Let's be clear that the dangers here are "no code review" and "no CI". The others are fine in most circumstances, unless you work on some huge monolithic codebase. Smaller cross-functional teams should be able to push to master to solve problems then and there without everyone's unanimous approval, and everyone should feel enough safety to be able to make changes to the codebase they share with their team. The real "root of all evil" is why is someone working against the team from within the team?