Creates well-formatted commits with conventional commit messages and emoji.
<emoji> <description>
Rules:
- Imperative mood ('add' not 'added')
- First line <72 chars
- Description body wrapped at 72 chars
- 1 blank line after first line
Description: Github emoji + most important key change.
Focus on the most important key change, avoid generic language!! Do not try to summarize all changes, just the most important one.
Provide a summary following by a bullet point list of the key changes made.
- π₯ Remove code or files
- π Fix a bug
- β¨ Introduce new features
- π Add or update documentation
- π¨ Improve structure/formatting of code
- π Deploy or performance improvements
- β Add or update tests
- π§ Add or update configuration files
- π¨ Refactor code
- π Add or update UI and style files
- π¦ Add or update compiled files or packages
- π· Add or update CI build system
- π Fix security issues
- β¬οΈ Upgrade dependencies
- β¬οΈ Downgrade dependencies
- π Add or update legal notices or license
- π₯ Introduce breaking changes
- π§ Work in progress
- β»οΈ Improve code reusability or maintainability
- π Temporarily disable linter or ignore warnings
βοΈ Offline