Add `gitcommit` and `gitrebase` language?

[spenserblack]

Language name

• Git Commit
• Git Rebase

URL of example repository

I think this is N/A, since a normal repository wouldn't commit any files that are in the .git directory.

URL of syntax highlighting grammar

• https://github.com/textmate/git.tmbundle/blob/master/Syntaxes/Git%20Commit%20Message.tmLanguage
• https://github.com/textmate/git.tmbundle/blob/master/Syntaxes/Git%20Rebase%20Message.tmLanguage

Most popular extensions

Likely N/A, but the filenames are

• COMMIT_EDITMSG
• git-rebase-todo

Detected language

None/Plain text

---

While the files themselves are unlikely to be present in a repository (there are a lot of results for COMMIT_EDITMSG, though), GitHub also uses linguist to highlight code blocks in Markdown, per my understanding.

Considering that these are common git use cases, I believe that the option to highlight their syntax in Markdown should be available. I think that GitHub should support syntax highlighting for git filetypes :laughing:

If it is reasonable to support syntax highlighting for these types of files, could you please consider it?

[Alhadis]

Sorry, we don't make exceptions to the rules. 😉 However, in this case, I don't think we have to: there are, indeed, a lot of results for COMMIT_EDITMSG files on GitHub, and even git-rebase-todo looks promising (only 869 results, but they appear to be well-distributed between users). So, you might be in luck.

[spenserblack]

Thanks for looking that up! I'm glad that it might not an exception to the rule after all :smiley:

[eric-wieser]

GitHub also uses linguist to highlight code blocks in Markdown, per my understanding.

What is the mapping between ```foo and the language chosen by linguist?

[spenserblack]

Wow, this issue is a blast from the past :laughing: Looking it up again, here are the relevant docs. I believe that the language's name or one of its aliases can be foo in this case.