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
I see that, in your contribution guidelines, you make mention to using conventional commits, which I think it's a fantastic guideline.
The "problem" is that I don't see any forcing of this rule. As an example, when making a pull request, one step of the CI is doing a commit lint.
Does it make sense to force this conventional commit rule harder? Of leave it as a recommendation?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I see that, in your contribution guidelines, you make mention to using conventional commits, which I think it's a fantastic guideline.
The "problem" is that I don't see any forcing of this rule. As an example, when making a pull request, one step of the CI is doing a commit lint.
Does it make sense to force this conventional commit rule harder? Of leave it as a recommendation?
The text was updated successfully, but these errors were encountered: