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
Often PRs are blocked because the commit-lint action fails - e.g. #304 fails because of commit-lint https://github.com/rhobs/observability-operator/actions/runs/5377063687/jobs/9760871220
It would reduce rework and toil if we provided a make target - commit-lint which allows contributors to validate commit messages locally.
make
commit-lint
It does help if all they have to run is make lint to ensure all lints are caught before submission.
make lint
The text was updated successfully, but these errors were encountered:
COMMIT_MSG_FILE=.git/COMMIT_EDITMSG
COMMITLINT=commitlint
lint-commit: @echo "Running commit lint..." @$(COMMITLINT) -e $$($(COMMIT_MSG_FILE))
we want something like this right?
Sorry, something went wrong.
No branches or pull requests
Often PRs are blocked because the commit-lint action fails - e.g. #304 fails
because of commit-lint https://github.com/rhobs/observability-operator/actions/runs/5377063687/jobs/9760871220
It would reduce rework and toil if we provided a
make
target -commit-lint
which allows contributors to validate commit messages locally.It does help if all they have to run is
make lint
to ensure all lints are caught before submission.The text was updated successfully, but these errors were encountered: