Style guide for writing GitHub commit messages.
No. | Emoji | Names | Example |
---|---|---|---|
01 | ✨ | update |
✨: Updated app workings |
02 | 🔨 | fix |
🔨: fix broken control header (#4) |
03 | 🤝 | patch |
🤝: update token signing method for HTTP requests (#12) |
️️04 | ⚡ | merge |
⚡: merge pull request from user/patch-1 |
05 | 🔒 | security |
🔒: move exposed API key to .env file |
06 | 🏷️ | label , tag |
🏷️: release v0.0.1 , 🏷️: v1.0.2 |
07 | 📝 | legal , markdown |
📝: update contributing guide |
08 | 📖 | docs |
📖: update docs with the new changes |
09 | 🔥 | restructure , rework |
🔥: redesign package workings |
10 | 🔮 | beautify , code style |
🔮: apply code styling to lib |
11 | 📦 | package , packager |
📦: update package.json and/or npm scripts |
12 | ⚖️ | legal , license |
⚖️: add GNU GPL v3 license ⚖️: update license year |
13 | 📍 | minor changes |
🤏: Changed a footer element |
14 | 🐛 | fix |
🐛: fix a bug |
15 | 🗼 | new |
🗼: added new cool stuff |
I think this is a good way to write commit messages also it looks good .