But how often do you need that for your personal projects? I just have a git repo on a server that’s accessible by ssh. I only use a web frontend when I have to share with other people and then you might as well use a free third party service.
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.
But how often do you need that for your personal projects? I just have a git repo on a server that’s accessible by ssh. I only use a web frontend when I have to share with other people and then you might as well use a free third party service.
You don’t need it on a server even. For simple versioning just use a local git repo without any bells and stuff
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.
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.