𝕨𝕒𝕤𝕒𝕓𝕚@feddit.de to Programmer Humor@lemmy.mlEnglish · 1 year agoWe've all been therefeddit.deimagemessage-square14fedilinkarrow-up1304arrow-down17
arrow-up1297arrow-down1imageWe've all been therefeddit.de𝕨𝕒𝕤𝕒𝕓𝕚@feddit.de to Programmer Humor@lemmy.mlEnglish · 1 year agomessage-square14fedilink
minus-squareNotSteve_@lemmy.calinkfedilinkarrow-up15·1 year agoHow do you accidentally force push lol
minus-square𝕨𝕒𝕤𝕒𝕓𝕚@feddit.deOPlinkfedilinkarrow-up22·1 year agoI assume the accident was not to force push, but to the wrong branch
minus-squaremagic_lobster_party@kbin.sociallinkfedilinkarrow-up15·1 year agoI hope they learned the value of protecting your branches.
minus-squareRedscare867@lemmy.mllinkfedilinkEnglisharrow-up3·edit-21 year agoThis is why I always git push origin +branch_name
minus-squareforgeddit@sopuli.xyzlinkfedilinkarrow-up1·edit-21 year agoMy go-to these days is to push the current branch, dynamically. git push origin HEAD Depending on the VC, HEAD has different prefix/suffixes to make it work. Edit: formatting, also I never checkout master I do origin/master so I cannot even push it with this method. I think
minus-squareDacoTaco@lemmy.worldlinkfedilinkarrow-up8·1 year agoI was wondering the same. Any branch that has any logic besides a ci build attached to it should have been force push protected by default…
How do you accidentally force push lol
I assume the accident was not to force push, but to the wrong branch
I hope they learned the value of protecting your branches.
This is why I always
git push origin +branch_nameMy go-to these days is to push the current branch, dynamically.
git push origin HEAD
Depending on the VC, HEAD has different prefix/suffixes to make it work.
Edit: formatting, also I never checkout master I do origin/master so I cannot even push it with this method. I think
I was wondering the same. Any branch that has any logic besides a ci build attached to it should have been force push protected by default…