I think it would be great to standardize (or at least widely adopt) some conventions for commit messages, especially with respect to tagging that isn't easily expressed by the "FOO: Imperative bar" style. Let's do it with plain text, not cute icons that get rendered differently (or not at all) depending on the OS or client you're on.
(Edit: Here's a link to a style guide in git's documentation, for example: https://www.git-scm.com/book/en/v2/Distributed-Git-Contribut...)
I like to keep Markdown away from my repos. After a while people get clever with their Markdown and it makes reading commit logs using command-line tools increasingly difficult. It also encourages writing things into commit logs that would be better suited for documentation.
Edit: apparently it's not a Github specific thing.
If this is a joke, eh it's not a great one.
If it's actually for real, might I suggest making a script for the emoji selection and the formatting of "Only One Newline"?
But :checkered_flag: for Windows? I think this is problematic. To me it looks more like an icon that suggests "finishing" something.
That's the problem with icons, their meaning breaks down rather fast if you can't create specific ones.
I've seen CI systems broken because of Unicode in git commit lines... :-/
On the plus side, I don't think this style guide will break your CI. It seems to be taking advantage of GitHub's text => emoji substitution, so other Git tools will just see the text form (eg. :sparkles:)
(e.g. :+1: means thumbs-up, but that's native to github / shows as :+1: to non-emoji-supported cli/browser/etc.)
It tends to act as resource management, you shouldn't be working on things that your manager doesn't know about at least enough to make an "issue" for it.
But it's not a 100% must in all cases, just that there SHOULD be a ref there. The rule of thumb for us was if it's going to take more than 15 minutes, it needs an issue.
I can't seem to reply any more, but this is just for organization. you can create your own issue and work on it on your own, this is just a way to organize and categorize the commits and provide an easy "parsable" way to give some context to them.
Gross. That sounds like process for process' sake. Or you could, you know, just trust that your developers are working on actually useful things because that's what you hired them to do, and we're all professionals here, one hopes.
Maybe something like this is useful for _very_ junior developers who need a bit of hand-holding before they're steeped in how professional development in a team setting works, but if you still need this sort of thing after even a year at work, that'd be a huge red flag to me.
Using emojis and limiting yourself to 50 chars is really difficult
Edit: Just seen that "Every Raw Emoji Text(:emoji:) is Counted as One Char!" - Great! But I'm not sure how Git CLI will like that.
Though it probably should.
8. Use the Present Tense ("Add feature" not "Added feature").
9. Use the Imperative Mood ("Move cursor to..." not "Moves cursor to...").
10. Use the Message body to explain what and why vs. how.
And why not emojis? They just won't be rendered where they aren't supported.
"*" = [the projects or repos to which this styleguide applies is not defined > /dev/null]
"Rule 8 parenthetical example ()" == "Use present participle as descriptor; try 'Adding feature' NOT 'Add feature' to accurately describe what submitter does during ``git commit``"
"Use the Imperative Mood" == "Error: Imperative Mood does not map to correct structure; please check grammar and re-submit"