Skip to content
New issue

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

Introduce commit message linting #89

Open
BeardOfDoom opened this issue Oct 7, 2020 · 0 comments
Open

Introduce commit message linting #89

BeardOfDoom opened this issue Oct 7, 2020 · 0 comments
Labels
🎉 Hacktoberfest 🍻 Hacktoberfest-friendly issues, great for newcomers.

Comments

@BeardOfDoom
Copy link
Collaborator

Brief

Once you start linting your code, there's no way back: you want to lint everything! For example, commit messages. Enforcing format and structure in commit messages allows for automatic semver bumps, changelog generation, repository analytics, and also looks good. See https://www.conventionalcommits.org/en/v1.0.0/

Because cryptid-js lacks this facility, we should definitely add commitlinting.

Task

@BeardOfDoom BeardOfDoom added the 🎉 Hacktoberfest 🍻 Hacktoberfest-friendly issues, great for newcomers. label Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎉 Hacktoberfest 🍻 Hacktoberfest-friendly issues, great for newcomers.
Projects
None yet
Development

No branches or pull requests

1 participant