nginx@lemmy.world to Lemmy Shitpost@lemmy.world · 1 month agoYeahlemmy.worldexternal-linkmessage-square69linkfedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkYeahlemmy.worldnginx@lemmy.world to Lemmy Shitpost@lemmy.world · 1 month agomessage-square69linkfedilink
minus-squarejustme@lemmy.dbzer0.comlinkfedilinkarrow-up0·1 month agoYou don’t need it on a server even. For simple versioning just use a local git repo without any bells and stuff
minus-square404@lemmy.ziplinkfedilinkEnglisharrow-up0·1 month 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-up0·1 month 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-up0·1 month 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-squaretrxxruraxvr@lemmy.worldlinkfedilinkarrow-up0·1 month agoTrue, I used the remote to access the code from other machines and/or as a remote backup. If you don’t need that, there’s no need for a server.
You don’t need it on a server even. For simple versioning just use a local git repo without any bells and stuff
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
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.
True, I used the remote to access the code from other machines and/or as a remote backup. If you don’t need that, there’s no need for a server.