Closed parazyd closed 3 years ago
Why do you think this is useful? You will have to motivate your changes. Do you typically have diffs in your commit messages?
Also we already have a section for COMMIT_EDITMSG
which sets the column marker to indicate when the commit message is too long. In fact, a proper commit message lexer could ensure that other commit message conventions (e.g. shorter subject line, empty second line etc.) are respected.
If you have git.commit.verbose set to true, then it shows you the entire commit in your $EDITOR. So this is where the diff can be colored.
This is useful when writing a commit message in git.