𝕨𝕒𝕤𝕒𝕓𝕚 to Programmer [email protected]English • 11 months agoWe've all been therefeddit.deimagemessage-square16fedilinkarrow-up1288arrow-down17
arrow-up1281arrow-down1imageWe've all been therefeddit.de𝕨𝕒𝕤𝕒𝕓𝕚 to Programmer [email protected]English • 11 months agomessage-square16fedilink
minus-square𝕨𝕒𝕤𝕒𝕓𝕚OPlinkfedilink18•11 months agoI assume the accident was not to force push, but to the wrong branch
minus-squaremagic_lobster_partylinkfedilink12•11 months agoI hope they learned the value of protecting your branches.
minus-square@[email protected]linkfedilinkEnglish2•edit-211 months agoThis is why I always git push origin +branch_name
minus-square@[email protected]linkfedilink1•edit-211 months 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-squareDacoTacolink7•11 months 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…
minus-square@[email protected]linkfedilink1•11 months agoGit rebase makes it possible getting used to do so
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…
Git rebase makes it possible getting used to do so