It would be too much to say that how core°hard word Git°hard word developers°hard word use Git°hard word is the correct way. But it is far safer to say that it is the orthodox way.
https://blog.gitbutler.com/how-git-core-devs-configure-git/
The results were very interesting, a rather concise°hard word list of 9 config°hard word settings and 3 aliases°hard word that the experiment°hard word participants°hard word more or less agreed should arguably°hard word be new defaults°hard word. Let's just take a look at the proposed°hard word config°hard word setting changes.
merge°hard word.conflictstyle°hard word = zdiff°hard word3
rebase°hard word.autosquash°hard word = true
rebase°hard word.autostash°hard word = true
commit°hard word.verbose°hard word = true
diff°hard word.colorMoved°hard word = true
diff°hard word.algorithm°hard word = histogram°hard word
grep°hard word.patternType°hard word = perl°hard word
feature°hard word.experimental°hard word = true
branch.sort = committerdate°hard word
Now, none of these have become the new defaults°hard word in the 3 or 4 years since this experiment°hard word, but it’s interesting that a lot of the Git°hard word developers°hard word themselves have a hard time using Git°hard word without several of these turned on.
Even more interesting is that most of you probably don°hard word’t know what any of these do.