Re:Jenkin developers accidentally do "git push --force" to o...
by jlgreco on Monday November 11, 2013 @06:06PM
(#6714729)
Ideally personal topic branches, not yet ready for world consumption, would be pushed but to a different repo. This would allow the main repo to have a global "No force pushes!" setting, and would prevent branch name collisions (how many developers have a scratch branch sitting around named 'scratch'?)
[ Parent
| on HN ]
Re:Jenkin developers accidentally do "git push --force" to o...
by crbnw00ts on Monday November 11, 2013 @09:05PM
(#6715413)
That's fine for some projects, but not every project follows that flow. One example: ompanies using GitHub Enterprise internally generally don't make every regular contributor to a project have their own fork (or at least they shouldn't, as it creates needless extra overhead). In that case, having some extra granularity around denying non-fastforward pushes to some branches but not others would be a helpful addition.