Re:Jenkin developers accidentally do "git push --force" to o...
by icebraining on Tuesday November 12, 2013 @04:25AM
(#6716715)
I don't think this is a black and white issue. It's not about denying all users the ability to express X ever again. I think it's more about having systems that can tell if X is an unusual or heavyweight action and say, "Hey, you're about to do X, which impacts a lot of stuff and you've never done before. Are you sure that's what you mean?"
Yes, but git already does that, by having the user type "--force". Asking would eliminate the possibility of scripting the action.
Re:Jenkin developers accidentally do "git push --force" to o...
by davvolun on Tuesday November 12, 2013 @05:42PM
(#6721890)
That's not entirely accurate, e.g. "git push --force --yes" would still be perfectly scriptable.
Re:Jenkin developers accidentally do "git push --force" to o...
by bereft_orange on Wednesday November 13, 2013 @10:11AM
(#6725599)
how far does that go though? `git push --force --yes --yes-I-am-absolutely-sure --by-pushing-this-commit-I-agree-I-am-paying-attention`. Seems like `--force` is a succinct way to cover those two parts.
Re:Jenkin developers accidentally do "git push --force" to o...
by gcb0 on Monday November 11, 2013 @08:36PM
(#6715312)
that's why a have a easy to type password to unlock my local private key, and i set my keymanager to never cache the password. It is always nice to have that last chance to review your changes to the VCS.
...not that it would have helped in this case as he was probably using it heedlessly in a jenkins plugin.
Agreed. From a usability perspective, undo is always best. Especially undo that the user: 1) knows about, 2) trusts, and 3) is fast. That encourages exploration and lets users fix mistakes.
> their mistake has now limited the actions that every other user of the system can make, because the system will be modified to prevent other users from making the same mistake.
I don't think this is a black and white issue. It's not about denying all users the ability to express X ever again. I think it's more about having systems that can tell if X is an unusual or heavyweight action and say, "Hey, you're about to do X, which impacts a lot of stuff and you've never done before. Are you sure that's what you mean?"
It's velvet rope permissions, not a locked door.