We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Similarly to mightyiam/eslint-config-love#840.
We could introduce an automated release process where each commit on master get evaluated following Conventional Commits.
master
We can use semantic-release for that purpose, it also automatically generates the changelog and publish the new version on npm.
npm
The text was updated successfully, but these errors were encountered:
Unlikely to be done.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Similarly to mightyiam/eslint-config-love#840.
We could introduce an automated release process where each commit on
master
get evaluated following Conventional Commits.We can use semantic-release for that purpose, it also automatically generates the changelog and publish the new version on
npm
.The text was updated successfully, but these errors were encountered: