Call me crazy, but I have never, EVER, had to type a single git command. I use Visual Studio Code with the Git Graph extension. It does everything for me without having to invest brain cells in learning a bunch of CLI commands.
Does it allow interactive rebase? Rebase onto another branch? Bisecting?
Pushing of a specific revision (not head)?
(I mention only actions I have to do regularly)
The issue I have had is that people don't know how to use their UI. This is true with command line as well, but then we would at least be in the same environment.
If we used the same GUI then that would be the same. But I find every GUI to be dangerous. They try their best to help but always make it easy to throw out unsaved changes (git hates doing this).
I have not found a git GUI where I don't need to spend mental energy getting the GUI to do what I want.
But I find every GUI to be dangerous.
I almost agree. I find most git GUI too dangerous. I use GitCola for basic things, I but almost always fall back to the good old cli.
Btw, new command learned! git switch -c new-branch
I normally run git stash ; git checkout -b new-branch ; git stash pop to achieve the same result.
Call me crazy, but I have never, EVER, had to type a single
git
command. I use Visual Studio Code with the Git Graph extension. It does everything for me without having to invest brain cells in learning a bunch of CLI commands.It's worth it because then you can pretend to be a hacker!
Does it allow interactive rebase? Rebase onto another branch? Bisecting?
Pushing of a specific revision (not head)?
(I mention only actions I have to do regularly)
Rebase for sure but don't ask me. Install it and see for yourself. If it suits you then great.
lol
I use that too but being old school have it's own level of satisfaction :P Cheers
So you depend on many others for minimal needed git things for CI/CD?
I have my minions for CI/CD, yes. I focus on programming, and then I let them lift that part for me. :-)
I work inside IDE, but use console for git just for fun.
If I should make some complex merge, then I prefer to use some GUI to be sure everything is going OK.
So you're not the go-to guy when things break in unexpected ways in your workplace.
Git-related? Usually not. But then again, under my eagle eye things don't break. :-)
The issue I have had is that people don't know how to use their UI. This is true with command line as well, but then we would at least be in the same environment.
If we used the same GUI then that would be the same. But I find every GUI to be dangerous. They try their best to help but always make it easy to throw out unsaved changes (git hates doing this).
I have not found a git GUI where I don't need to spend mental energy getting the GUI to do what I want.
Btw, new command learned!
git switch -c new-branch
I normally run
git stash ; git checkout -b new-branch ; git stash pop
to achieve the same result.But
switch -c
andcheckout -b
are the same. They both requirestash
if git needs to update a modified file.