- 🍕 Feature - A new feature.
- 🐛 Bug Fix - self-explanatory
- 📝 Documentation Update - Documentation and related changes.
- 🎨 Style - Changes that do not affect the meaning of the code; for example, white space, formatting, or missing semicolons.
- 🧑💻 Code Refactor - A code that neither fixes a bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name).
- 🔥 Performance Improvements - A code change that improves performance.
- ✅ Test - Added | Modified | Removed tests
- 🤖 Build - Changes related to code building (e.g. adding npm dependencies or external libraries).
- 🔁 CI - Changes that affect the build CI/CD pipeline
- 📦 Chore - Changes that do not affect the external user (e.g. updating the .gitignore file or .prettierrc file).
- ⏩ Revert - self-explanatory
- 👷♀️ Created small PR.
- 👴🏻 No deprecated or outdated code is introduced
- 💭 Code is self-documenting. Comments are unnecessary and should only be used to explain why a decision was made
- 🗒️ Methods are documented with JS Doc including description, params, and return type
- 📋 The commit message follows our guidelines
- 👌 The pull request description explains any decisions or trade-offs made regarding code quality and design
- 🔖 The branch follows our naming guidelines
- 👓 I have followed the style guidelines of this project
- 🤳 I have performed a self-review of my code
- 🏷️ I have correctly labelled PR & added Ticket Number
- 🙆♂️ I have cleared the Acceptance Criteria
-
⚠️ My changes generate no new warnings
- 👍 yes, new and existing unit tests pass locally with my changes
- ♻️ had to make changes to existing tests
- 🥹 no, because I need help
- ⏮️ some existing tests are failing
- ⌛ no time to add tests
- 🙅 no, because they aren't needed
- 📜 README.md
- 📝 Confluence
- 🙅 no documentation needed