DEV Community

Discussion on: why branching on git is wrong

Collapse
 
mortoray profile image
edA‑qa mort‑ora‑y

Based on various comment replies you've made it sounds like you're working in a dysfunctional environment.

Then you realize is 4am and all of you are still on the office because two guys on their bubble made architectural decisions that impacted

You don't appear to be communicating, not just effectively, but at all.

Communication problem are unavoidable or so says my experience.

Good communication, through tools, talking, meetings, whatever, is the key to good development. It sounds like you've given up on communicating.

If you have a good CI system (it's 2018 we all should have one) nothing untested nor unclean code enters the repo.

CI's can't test code cleanliness. The idea of full coverage is also a bad myth.

then reality comes and some people don't even listen on the daily standup much less take a look at slack or whatever they just want to be left alone and code.

Why are you guys even working on the same team if this is the case?

In my personal experience PRs are almost useless unless all your team knows how to do them well.

You're programmers, you should know about pull-request workflows.

The problem with branching is that it actively requires the developers to be clean.

Why would you not want developers to create clean code? I'd prefer my processes to encourage clean code always.