3 ms·
I was about to go in fully to this style at most ~2 weeks ago. It's another forcing function to be cognizant of what exactly you're working on at a given time.
by DivisionSol 7y ago
I was about to go in fully to this style at most ~2 weeks ago.
It's another forcing function to be cognizant of what exactly you're working on at a given time. (Speaking from JavaScript land,) don't update the packages, fix two bugs, add a couple features, refactor some code all in the same commit. When things go wrong in a few months, your bisect will land right on that big blob of things. In the vein of focusing on things it's also nice when reviewing code. Ideally reducing the amount of times someone sneaks in a random 'bug fix' that eventually needs to be tracked down and added to the spec.
Also, the idea of being able to categorize all commits into their respective buckets between releases. A similar idea from the other commit message prepend style out there, but with emojis. Grep for all :sparkles: and :bugs: and you have your patch notes.
But, as I started with, I couldn't commit, (heh). Terminal + `zsh` on MacOS Catalina seems to refuse to format emojis properly, often resulting in console frustrations as spaces disappear and emojis overlap text. If anyone knows a fix, let me know!
- larusso 7y agoInstead of grep for :sparkles: etc you can also just grep for any other prefix style. The biggest turn down for me is the fact that these emojis render differently on each platform. It’s hard to transpose meaning for an icon that is not static in its visual.