You also left out a lot of the (again simple) commands I've included — switching branches and partial commits, where things like fuzzy autocomplete are very nice if your shell does not hook into Git and support fuzziness.
git checkout -b new_branch
<edit edit edit>
git commit -a -m "i'll merge this branch"
git checkout master
git merge new_branch
vs: git checkout -b new_branch
<edit edit edit>
git commit -a -m "did stuff that i'll rebase this time"
git fetch
git rebase origin/master
git checkout master
git merge new_branch
vs: git checkout -b new_branch
<edit foo.txt and bar.txt>
git add foo.txt
git commit -m "edited foo"
git stash
...
People think differently, but nothing you've described is conceptually different than using the CLI. It's just a GUI, doing/obscuring the same stuff -- stuff that you need to understand to use git.In other words, it's the leaky abstraction problem. You can pretty up the UI, but ultimately, you have to communicate the concept to the user. It's how we got those "Can I copy The Internet?" questions in Windows 95....
Then I'll switch over to the CLI for branching, merging, resetting and bitsecting (the latter two arent possible in the GitHub app)
cd /yor/src/dir
bash: cd: /yor/src/dir: No such file or directory
examines closely to look for typo
cd /your/src/dir <edit stuff>
git diff
git comit -m "edited stuff"
Did you mean this? git: 'comit' is not a git command. See 'git --help'.
Did you mean this?
commit
git commit -m "edited stuff"I think this is enough to get the picture.
And on anecdotal evidence, I've observed that people who use git intensively everyday often have aliases to these commands that have a low probability of typos.
eg gcom => git commit
I mean...I sort of get why people do git integration in editors (even thought it tends to lead to ignorance of git), but opening up another, non-console, non-editing app, just for git?