4 ms·
> almost never ... actually lost code That seems like one of the absolute basics. "Almost" never...? > I just make a backup copy of the directory in case I sc
by jfk13 4y ago
> almost never ... actually lost code
That seems like one of the absolute basics. "Almost" never...?
> I just make a backup copy of the directory in case I screw up irrevocably
If you really felt you could trust your source control system, that shouldn't be needed, and...
> the cases where I've need to use my backup copy
...should be nonexistent.
- copperx 4y agoI agree. If losing code with Git is even a remote possibility, then you're "holding it wrong" indeed.
- Dylan16807 4y agoThere are multiple ways to accidentally overwrite or delete a file that wasn't committed yet. There are also situations where you need to use these commands and you're not ready to commit everything. The safe way to handle this is generally making a stash commit and immediately applying it, but if you don't know that, or don't think to do that first, the result can be data loss. Git is very careful about commits but if you never staged something then git can be ruthless.
- agentwiggles 4y agoI guess what I'm trying to express is that even in the rare case I'm doing something fancy with git making sure I don't lose anything is trivial. I can think of exactly one time I actually lost code and I was doing ill advised reflog fuckery. I take your point, but I stand by my opinion that in virtually all normal usage, git just isn't that hard. YMMV.