📝 Update commits guide #75
Conversation
|
Needs #76 so that emojis don't break the linter. |
dankolbman
force-pushed
the
update-commits
branch
4 times, most recently
from
7e4edcf to
f111311
Compare
dankolbman
force-pushed
the
update-commits
branch
from
f111311 to
9dfb865
Compare
| counting the markdown tag emoji as only one charecter) line summarizing the | ||
| nature of the commit. | ||
| It should start with an appropriate emoji followed by a space | ||
| then a short summary of the change made in the commit. | ||
| When adding an emoji to the commit message, use the colon-ated version as | ||
| opposed to the actual unicode symbol, eg: `:sparkles:`. For inspiration of what |
There was a problem hiding this comment.
The set of systems that understand unicode is much larger than the set of systems that dynamically convert shortcodes to their glyphs. Using shortcodes guarantees that git log won't show them properly, whereas all a person needs to do to ensure glyph display is join the past two decades with a unicode-capable font.
There was a problem hiding this comment.
Using shortcodes guarantees that git log won't show them properly
What do you mean won't show them properly? Bc of line length or bc it won't render the glyphs?
There was a problem hiding this comment.
doesn't convert shortcodes into glyphs
There was a problem hiding this comment.
yea git log doesn't but our terminals render them correctly. i thought thats what we saw the other day
There was a problem hiding this comment.
terminals render unicode emojis. terminals do not convert ascii shortcodes into unicode emojis.
There was a problem hiding this comment.
copy and paste ":smile:" into your terminal and see what it prints. now paste 😄. Only the latter will actually show a picture of a face.
Updates commit guide with some results following discussion on git standards.