conventional-changelog-emojis
Advanced tools
Use emojis in your commit message for fun and profit!
The convention is based on Angular's Commit Message Guidelines.
<emoji> <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
You can find the supported emojis and their meaning here.
Appears under "Features" header, pencil subheader:
✨ add 'graphiteWidth' option
Appears under "Bug Fixes" header, graphite subheader, with a link to issue #28:
🐛 stop graphite breaking when width < 0.1
Closes #28
This preset supporst mulitple smart commit formats.
If a smart commit references an issue with the # prefix (This is supported by conventional-changelog by default) they will be linked in the generated changelog.
If a smart commit references an issue with the ABC- prefix they will be linked in the generated changelog.
If your issue tracker has a different URL than your repository (e.g. your using Bitbucket and track issues in Jira), you can specify this in your package.json via the bugs.url field.
This preset supports Jira Smart Commits
Based on the conventional-changelog-angular preset.
FAQs
conventional-changelog preset with emojis
We found that conventional-changelog-emojis demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.