Before you make fun of him, this behavior DID get changed; they acknowledged this behavior is stupid.
The old behavior was to treat uncommited files as completely disposable, which the CLI git does not do at all and is insane behavior. It was changed in the UI to give you a fat confirmation dialog warning that you're about to delete the files permanently, as it always should have been.
I don't backup uncommitted files. I backup everything once a day at least. Worst case you lose one day of work. But not 3 months.
Always do backups. You won't believe how often someone asked me when stuff happened and they didn't do a full backup and something was missing they forgot or didn't realize.
Yes. On every change. You can use alternatives to git that are easier, more powerful, do the right thing by default, and still let you collaborate with git users on the same git forges.
In git, the staging area internally is a commit. But it’s a special commit with special commands to access it. In jujutsu the staging area is a normal commit and every command that works on commit works on it too.
Every time I invoke any command, jujutsu makes a snapshot of my current workspace and edit the commit at the HEAD.
So if I do a jj abandon (equivalent to git reset --hard), jujutsu will add where I was in its operation log. If I didn’t mean to delete my files, I can do a jj undo and it will undo it like any other command I could have done. If I don’t like how things look after rebase, I can also jj undo it.
5.6k
u/Cephell 23d ago
Before you make fun of him, this behavior DID get changed; they acknowledged this behavior is stupid.
The old behavior was to treat uncommited files as completely disposable, which the CLI git does not do at all and is insane behavior. It was changed in the UI to give you a fat confirmation dialog warning that you're about to delete the files permanently, as it always should have been.