Hello, I agree with you that knowing the commands is essential.
From my experience though, I actually learned Git branching, rebasing and all that more complex stuff, by observing what the GUI did.
Yes, you still need to learn the documentation yourself and try it out in the CLI, but Git really was overwhelming at first and the GUI really helped me a lot to visualize what on Earth was going on.
Now I'm still using a GUI, for productivity. Solving a merge conflict in Vim/CLI? Massacre. Doing rebase and squash on a branch with 50+ commits? Sorry, nope.
Yes, I do agree that a GUI helps in observing changes in files. rebases among other things. I often use the GIT GUI the IDE brings (VS code or other) in order to do that.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hello, I agree with you that knowing the commands is essential.
From my experience though, I actually learned Git branching, rebasing and all that more complex stuff, by observing what the GUI did.
Yes, you still need to learn the documentation yourself and try it out in the CLI, but Git really was overwhelming at first and the GUI really helped me a lot to visualize what on Earth was going on.
Now I'm still using a GUI, for productivity. Solving a merge conflict in Vim/CLI? Massacre. Doing rebase and squash on a branch with 50+ commits? Sorry, nope.
Yes, I do agree that a GUI helps in observing changes in files. rebases among other things. I often use the GIT GUI the IDE brings (VS code or other) in order to do that.