For another perspective: It's been maybe 6 years of pretty consistent commandline usage, and I pretty much do not have to look up anything.
I usually do feature branches, so the operations Im talking about are push/pull, commit, merge, rebase, bisect, and cherry-pick. They each have a few flags, and a few positional arguments.
Realistically, they dont have to be intuitive. You learn them once by going through a small book like the git book, and you wont really forget them if you use them regularly.
The checkout/reset concept is severely and confusingly overloaded/overlapping. Addition is confusing as well, although not to that extent.
Changes can be in many states, and many operations can be applied (all the permutations of: in/off index, deleted, changed, added), but the UX has never been (re-)designed for usability, so that it's extremely confusing to remember what to use.
As I said, I have a totally different experience. I never had a day where it 'clicked' or anything, I just feel I understood the model and now it makes sense.
Agreed, I use command line for basic tasks, then git-cola for committing for a basic UI.
Before git I used svn, and must say the main thing I'm happy about git is how easy it is to just push a repository wherever, and GitHub having perfect timing to help it become a staple (at the time they didn't have private repos, but was still good).
I have a whole bunch of shell aliases for my day to day use, mostly around branches (where I work we use GitHub, and opensource projects who use git use branches for PRs/MRs/etc).
Comments
It's been 10 years and I still need to look up the most basic things in git. It's just not intuitive to me at all.
Had fossil recommended to me. Also read their fossil vs git page, and I found myself agreeing with everything they said.
https://fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki
For another perspective: It's been maybe 6 years of pretty consistent commandline usage, and I pretty much do not have to look up anything.
I usually do feature branches, so the operations Im talking about are push/pull, commit, merge, rebase, bisect, and cherry-pick. They each have a few flags, and a few positional arguments.
Realistically, they dont have to be intuitive. You learn them once by going through a small book like the git book, and you wont really forget them if you use them regularly.
I recommend doing this.
The checkout/reset concept is severely and confusingly overloaded/overlapping. Addition is confusing as well, although not to that extent.
Changes can be in many states, and many operations can be applied (all the permutations of: in/off index, deleted, changed, added), but the UX has never been (re-)designed for usability, so that it's extremely confusing to remember what to use.
As I said, I have a totally different experience. I never had a day where it 'clicked' or anything, I just feel I understood the model and now it makes sense.
Agreed, I use command line for basic tasks, then git-cola for committing for a basic UI.
Before git I used svn, and must say the main thing I'm happy about git is how easy it is to just push a repository wherever, and GitHub having perfect timing to help it become a staple (at the time they didn't have private repos, but was still good).
I have a whole bunch of shell aliases for my day to day use, mostly around branches (where I work we use GitHub, and opensource projects who use git use branches for PRs/MRs/etc).
It's been 10 years and I don't have to look up most commands in git.
You say the most basic commands, I don't understand how git add, commit, push, pull, fetch would require a look up.
I have to look up how to create and switch to branches every single time.