21–30 of 39 posts
> Use Valid MarkDown format in Message Body. 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.
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.
But why?
Oh, please don't... I've seen CI systems broken because of Unicode in git commit lines... :-/
I'm not a huge fan of mandatory emoji in commit messages either, but this is a poor excuse. A Git commit message can contain any sequence of bytes except for a NUL byte. It can even contain invalid UTF-8. Tooling that doesn't treat commit messages like this is dangerously fragile. God forbid anyone accidentally pastes “typographer’s quotes” or text with diacritics into a commit message and breaks the build. On the pl…
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...)
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.