I tend to write (some) tags in the same subject-body format as commits. There's also NOTES_EDITMSG, but I don't think that the commit style really lends itself to that so I left it out.
Detect TAG_EDITMSG as gitcommit
Signed-off-by: Jack Nagel <firstname.lastname@example.org>
Does this really make sense? conf seems more than adequate, and that happens without us doing anything.
If it does, this needs to be squared away with 1b9c234.
@tpope How about MERGE_MSG?
Recent versions of git default to interactively editing the merge
commit message (like git merge --edit), which opens .git/MERGE_MSG.
This creates git commit objects, so it seems logical to set the filetype
git merge --edit
I forgot about this, and I don't really care anymore.
There are situations where I could see this making sense—there are git commands (git tag -n, for example) which show the first line of a tag message by default in a similar "email subject-like" way as other commands show the first line of commit messages, so it seems to follow that they could benefit from an application of the same standards as a commit message.
git tag -n
Highlight TAG_EDITMSG as a commit