nginx@lemmy.world to Lemmy Shitpost@lemmy.world · 2 days agoYeahlemmy.worldexternal-linkmessage-square82fedilinkarrow-up1666arrow-down122
arrow-up1644arrow-down1external-linkYeahlemmy.worldnginx@lemmy.world to Lemmy Shitpost@lemmy.world · 2 days agomessage-square82fedilink
minus-square404@lemmy.ziplinkfedilinkEnglisharrow-up7·2 days agoOne of the most useful features is rolling back from origin when you’ve borked your local repo (not that I ever have…)
minus-squarejustme@lemmy.dbzer0.comlinkfedilinkarrow-up1·2 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-square404@lemmy.ziplinkfedilinkEnglisharrow-up1·14 hours 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
minus-squaretrxxruraxvr@lemmy.worldlinkfedilinkarrow-up3·1 day 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.
One of the most useful features is rolling back from origin when you’ve borked your local repo (not that I ever have…)
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
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~11instead ofHEAD~1I’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.