4 ms·
On an Enterprise project I was on recently this was a real problem. With about 12 distinct and large (5-10 developers per team) all working on a single git repo
by fmstephe 14y ago
On an Enterprise project I was on recently this was a real problem. With about 12 distinct and large (5-10 developers per team) all working on a single git repo, the lingering branches were out of control. They had built up over more than a year of abuse.
I think this issue is worth thinking about. For projects with a single owner or a small core set of contributors taking pull requests it is manageable. But when the responsibility is distributed, especially in the degenerate culture of Enterprise Java, uncontrolled branching can make git usage miserable.
The real problem was that we were using Git like an SVN server. But it was really interesting to see how bad it can be when branch pruning is not considered upfront.
Great feature github :)
- judofyr 14y agoDid you consider using forks more actively? E.g. each team has it's own fork where they commit, and one person is responsible for merging the fork upstream?
- snprbob86 14y agoI second this. We really enjoyed the one fork per user model. Each fork's owner was responsible for their own branches, which was much more manageable.
- tux1968 14y agoThat's really the way Git was designed to be used. Trying to use Git in an SVN model is doable, but suboptimal and likely to lead to the types of issues the parent comment was complaining about.