nginx@lemmy.world to Lemmy Shitpost@lemmy.world · 4 days agoYeahlemmy.worldimagemessage-square83fedilinkarrow-up1680arrow-down120
arrow-up1660arrow-down1imageYeahlemmy.worldnginx@lemmy.world to Lemmy Shitpost@lemmy.world · 4 days agomessage-square83fedilink
minus-squarejustme@lemmy.dbzer0.comlinkfedilinkarrow-up1·4 days agoI’m not that accustomed with it myself, so my question: how can you bork your local repo so you can’t roll back? Did you tinker in the .git folder? xD
minus-squaretrxxruraxvr@lemmy.worldlinkfedilinkarrow-up3·3 days agoI’ve had colleagues who’d panic when they had merge conflicts, then fuck something up, remove the whole dir and create a new clone. If you’re competent I don’t think it should be necessary.
minus-square404@lemmy.ziplinkfedilinkEnglisharrow-up1·3 days agoThere are many ways. Like the other user said, fucking up a merge/rebase then fucking up the merge abort. Or (one of my personal favorites) accidentally typing git reset --hard HEAD~11 instead of HEAD~1
I’m not that accustomed with it myself, so my question: how can you bork your local repo so you can’t roll back? Did you tinker in the .git folder? xD
I’ve had colleagues who’d panic when they had merge conflicts, then fuck something up, remove the whole dir and create a new clone. If you’re competent I don’t think it should be necessary.
There are many ways. Like the other user said, fucking up a merge/rebase then fucking up the merge abort.
Or (one of my personal favorites) accidentally typing
git reset --hard HEAD~11
instead ofHEAD~1