Breaks git commit -v (git commit --verbose)

According to the documentation for git-commit (emphasis mine)

-v –verbose Show unified diff between the HEAD commit and what would be committed at the bottom of the commit message template to help the user describe the commit by reminding what changes the commit has. Note that this diff output doesn’t have its lines prefixed with #. This diff will not be a part of the commit message.

Git is apparently able to ignore the diff block thanks to a marker preceding it, which looks like this:

# ------------------------ >8 ------------------------
# Do not touch the line above.
# Everything below will be removed.
#

Today I’ve discovered that the plugin causes the full diff to be included in the commit message (disabling/uninstalling it fixes the problem.) I’m assuming it must be messing with the “Do not touch the line above.” line, causing Git to get confused.

I could add a [COMMIT_EDITMSG] section to my .editorconfig file to try and have this file left alone, but this feels hackish. Furthermore, adding this to every repository would get tiresome.

I wonder if there is a more elegant solution to this. git commit -v is just too good to give up!

In case it matters, this is my .editorconfig file:

root = true

[*]
end_of_line = crlf
indent_size = 4
indent_style = space
insert_final_newline = true
trim_trailing_whitespace = true

---

IssueHunt Summary

vogu66 has been rewarded.

Backers (Total: $40.00)

• issuehunt ($40.00)

Submitted pull Requests

• #88 Solve issue #55 with lf line endings in .git folders

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[sindresorhus]

Could just ignore the COMMIT_EDITMSG filename in this plugin.

[issuehunt-app[bot]]

@sindresorhus has rewarded $36.00 to @vogu66. See it on IssueHunt

• 💰 Total deposit: $40.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $4.00