Geared for dotfile and colorscheme tinkerers.
I wasn't satisfied by the existing emoji commit standards, because they are more geared towards coders than people just maintaining dotfiles and only occasionally contributing a bug report or a piece of documentation (e.g. I don't need an emoji for tests, because I don't do any).
Here is my own standard, modelled after my own usage (feel free to use it as well if you want):
- π¬
:clapper:
= Initial commit1 - π
:new:
= Add stuff - ποΈ
:wastebasket:
= Remove stuff - βοΈ
:pencil2:
= Fix a typo or spelling mistake - π
:page_facing_up:
= Add documentation - π
:bug:
= Fix a bug or anything that might unintentionally break my dotfiles or colorschemes - π§
:wrench:
= Adjust, improve or perfect parts of existing config - π¨
:art:
= For cosmetic changes (e.g. changing some colors of a colorscheme) - β¨
:sparkles:
= Add something fancy (e.g. something that makes the repo look cool, like badges or decorative images) - πΌοΈ
:framed_picture:
= Add screenshot - β²οΈ
:timer_clock:
= A temporary change that will be undone e.g. once a problem is definitely solved - β
:exclamation:
= A major change that makes the new version radically different from the previous β οΈ :warning:
= experiment (i.e. something I'm just trying out, that is a commit highly likely to be reverted)2.- π¦
:package:
= A new release (for stuff that absolutely requires releases when you change anything at all)
License: MIT
- 1: Why most commit emoji standards use π
:tada:
instead is beyond me. After all, the initial commit isn't such a big deal, so the tada seems like premature celebration. I feel that an initial commit is the first step of a big endeavor, similar to how using the movie clapper for the first time used to signify the start of the movie project. - 2: Where is the test tube emoji when you need it?