:git-emoji: <subject>
<body>
- A message consists of a git-emoji and subject
- Body messages are optional
- No line should be longer than 50 characters long, for optimal github viewing
:sparkles: (Introduce new features)
:fire: (Remove code or files)
:bug: (Fix a bug)
:zap: (Improve performance)
:recycle: (Refactor code)
:lipstick: (Update style; formatting, missing semi-colons, white-space, etc)
:wrench: (Add or update configuration files)
:building_construction: (Make architectural changes)
:white_check_mark: (Add or update tests)
:memo: (Add or update documentation)
:bulb: (Add or update comments in source code)
:construction: (Work in progress)
:poop: (Write bad code that needs to be improved)
- Use the imperative, present tense: "Add" not "Added" nor "Adds"
- Capitalize only in first letter except for proper noun: "Add NFTReceiver function" nor "Add NFTReceiver Function"
- Don't use (.) at the end
- Separate subject from body with a blank line
- Use the body to explain what and why vs. how
- Can use multiple lines with "-" or "*" for bullet points in body
✨ Add NFTReceiver function
🔥 Remove deposit function
🐛 Fix a bug
⚡ Improve performance
♻️ Refactor code
💄 Remove space lines
🔧 Use variable expansion in doetnv files
🏗️ Split into 2 files
✅ Test required
📝 Update READMEs
💡 Add comments
🚧 Work in progress
💩 Need improvements