I have only been using it for ~ 4 years and the UX seems pretty logical even for not-basic cases.
Maybe because it was only my second VCS[1], it didn’t seem at all problematic to me. On the contrary, every time, I just found myself going “nice”, whenever I found a new feature.
When it comes to git restore ., well, you won’t use rm -rf * in your working directory, right?
I haven’t used git based GUIs much. Some of the functions that my IDE provides, I use now and then.
Being able to see the git blame for a file, right in place, scrolled to the same line as I was looking at the code, helps quite a bit (and so does the git based annotations).
But for things like commit, restore, pull, push, rebase and things that will write something, I just use the CLI, because I feel like I know what is going to happen ad that gives me confidence.
I have only been using it for ~ 4 years and the UX seems pretty logical even for not-basic cases.
Maybe because it was only my second VCS[1], it didn’t seem at all problematic to me. On the contrary, every time, I just found myself going “nice”, whenever I found a new feature.
When it comes to
git restore .
, well, you won’t userm -rf *
in your working directory, right?I haven’t used
git
based GUIs much. Some of the functions that my IDE provides, I use now and then. Being able to see thegit blame
for a file, right in place, scrolled to the same line as I was looking at the code, helps quite a bit (and so does the git based annotations).But for things like
commit
,restore
,pull
,push
,rebase
and things that will write something, I just use the CLI, because I feel like I know what is going to happen ad that gives me confidence.the first one being folders with timestamps ↩︎