Even if they cater to novice users, they aren’t novice users themselves and lack of experience is no longer an excuse when Git wrapper authors make bad choices about defaults.
The main problem is that many people just don’t care, and view VCS as an afterthought, after the actual work is done. They don’t even know how powerful git can be when used optimally.
Maintaining a clean git history is work. You have to think about it, and invest into it. But it is well worth it, in the mid to long term.
I understand different projects have different requirements for version control, but as someone who does not work on massive codebases with a huge amount of collaborators I enjoy that the GUI I use somewhat hides the complexity I don’t want to engage with.
Merged master into master
commits
they make it the default to merge current branch into current branch (pull with merge) and they default to committing large amounts of code under a simple message.
i know fulltime devs who use git every day, who have no idea what a rebase is - they think merge does what really rebase does, and thats mostly the fault of bad defaults.
git commit -p should be the default committing interface also; assuming you like git history which can be bisected, reverted, etc.