At least always use git push —force-with-lease
. It makes sure you are that the remote hasn’t changed since you lasted pulled. git-scm.com/docs/git-push#Documentation/git-push.…
Openheimer in programming
Submitted 1 year ago by mastermind@lemm.ee to programmer_humor@programming.dev
Comments
mikazuki@lemmy.world 1 year ago
lobut@lemmy.ca 1 year ago
I mean, it should be a protected branch to prevent against that.
BeigeAgenda@lemmy.ca 1 year ago
Sometimes there’s no other option when someone merged develop into master just before a critical bug was found.
F04118F@feddit.nl 1 year ago
You can always revert (i.e. undo in a new commit) the faulty commit. That will keep the history. This meme is not just about pushing straight to master, it’s about
push --force
which overwrites the remote branch completely, changing history.