3 ms·
That said, sometimes Bad Thing Prevention is something that should have been implemented long ago, and was hitherto unrecognized. My canonical example is increa
by btown 13y ago
That said, sometimes Bad Thing Prevention is something that should have been implemented long ago, and was hitherto unrecognized. My canonical example is increased regulations and requirements for entry when an untrained student was seriously injured in a university machine shop; training is something that can be attained, just as "being the one at the top of the organization with force push access" is something that can be attained. There's no loss of abilities, just a more-optimal mapping of abilities to the people who know how to use them.
- bad_user 13y agoGiven that Git is such an integral part of the workflow, I find unnacceptable the ability to push to the central repo for people that can't handle Git well. Git is distributed, if you're using it like it's SVN you're doing it wrong. And yes, we all make mistakes. But by Git's nature, lo and behold, everybody has a copy.
- ihateloggingin 13y agoThis has nothing to do with git. It has to do with github. Git already prohibits forced pushes if you use 'git init --shared' to create your repo.