3 ms·
> some other colleagues had misused a forced push Git has a learning curve. Atlassian Stash comes with a plugin that exposes a "Disable Force Push" toggle. I
by taspeotis 13y ago
> some other colleagues had misused a forced push
Git has a learning curve.
Atlassian Stash comes with a plugin that exposes a "Disable Force Push" toggle. I have that on for all the repositories it hosts. Nobody complains that force push doesn't work (~10 devs) because if you're doing force push you're probably doing something wrong.
- twic 13y ago>> some other colleagues had misused a forced push > Git has a learning curve. That sounds a bit like a euphemism for "is hard to use". However, that's not what i'm getting at. The first pair of people misused a forced push because they're clowns. They are never going to learn to use any version control system properly, even if the learning curve was down a slide. If we disabled force push, they'd probably have reenabled it (they're sysadmins, so it would be hard to stop them). The problem is that the second pair of developers, who are not clowns, but are also not Git power users, nor have any interest in becoming Git power users, got screwed by the first pair's mistake, and could only have got out of it by using an obscure feature known only to Git power users.
- Skinney 13y ago> and could only have got out of it by using an obscure feature known only to Git power users. Obscure? I spent one afternoon reading the Pro Git book that is available free online. The first thing you learn, after learning to alter history, is the reflog. Look, everything people in our business do is based on trust. It's fairly easy to mess up for everyone, and this includes Mercurial as well. Like switching bookmarks around or messing with hg strip.