I find commits very relevant when grokking unfamiliar codebases. The history and changes (plus, how they're documented) are half the battle for me in that conte

I find commits very relevant when grokking unfamiliar codebases. The history and changes (plus, how they're documented) are half the battle for me in that context. The article mentions the use of line-length and commit-templates. Personally, I have my .vimrc [0] configured to handle columns for commits (50 for the title & 72 for the body). Then, in my .gitconfig [1] I set a template [2] to be used for all commits. It's a relatively minimal addition, but it's improved my CLI experience with Git immensely. [0]: https://github.com/Pinjasaur/dotfiles/blob/89ca76eaaef24165e877e51ddd524f79e16f3ca1/.vimrc#L89-L99 https://github.com/Pinjasaur/dotfiles/blob/89ca76eaaef24165e... [1]: https://github.com/Pinjasaur/dotfiles/blob/89ca76eaaef24165e877e51ddd524f79e16f3ca1/.gitconfig#L71 https://github.com/Pinjasaur/dotfiles/blob/89ca76eaaef24165e... [2]: https://github.com/Pinjasaur/dotfiles/blob/89ca76eaaef24165e877e51ddd524f79e16f3ca1/.gitmessage https://github.com/Pinjasaur/dotfiles/blob/89ca76eaaef24165e... Edit: fix link formatting