sure except that suddenly you do not know why you have to know the arcanes
part. I think that git is not layered so you get exposed to a lot of details even when you avoid.
Hmm, I don't see that, but I've been using git for many years so I am not in position to judge it how complex it is.
May be having a set of git macros would help.
Maybe not because macros are fragile and your average set of git commands is rather limited. Making git simpler through Pharo could be nice...
Maybe providing a way to streamline common patterns. For example in git community there's a well known workflow model http://nvie.com/posts/a-successful-git-branching-model/ There's even git extension (but you can still use git directly) on top of that pattern https://github.com/nvie/gitflow (better visualized here https://danielkummer.github.io/git-flow-cheatsheet/ ) And while most don't follow the pattern strictly, most people are at least inspired by it and adapt parts of it. Peter