-
Notifications
You must be signed in to change notification settings - Fork 915
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
fix: commitlint --last
fails
#3981
Comments
/cc @knocte |
@mfcollins3 thanks for reporting this bug, we'll look at it on Monday. |
…est for running with --last flag. See [1]. Added regression test for running with --last flag. See [1]. [1] conventional-changelog#3981
Added regression test for running with --last flag. See [1]. [1] conventional-changelog#3981
Added regression test for running with --last flag. See [1]. [1] conventional-changelog#3981
Added regression test for running with --last flag. See [1]. [1] conventional-changelog#3981
Fixed regression [1] when using --last flag. [1] conventional-changelog#3981
Fixed regression [1] when using --last flag. [1] conventional-changelog#3981
Fixed regression when using --last flag. Fixes conventional-changelog#3981
This might still be happening:
|
@schimini can you give us access to that repo? can we fork it or...? |
@knocte yes check here: https://github.com/schimini/strapi happened basically with all my commits. |
@schimini
If I try to install
Node.js v18.19.1 |
Hmm that's weird :o my setup is:
|
|
@webwarrior-ws I am clueless I tried the latest even and it ran with no problems
|
@schimini |
@webwarrior-ws ha ha! |
Steps to Reproduce
I created a valid commit message and used the
npx commitlint --last --verbose
command to validate the commit message as shown here. I received the following errors:subject may not be empty [subject-empty]
type may not be empty [type-empty]
The commit message was:
ci: validate commit messages
I added development dependencies on commitlint and husky. commitlint is
being used to validate commit messages conform to the Conventional
Commits format and follow the configured rules for the project. husky is
being used to run commitlint on every commit using the commit_msg Git
hook.
I created the setup.sh script to automate the steps to install the
project dependencies after cloning the repository.
I updated README.md with instructions on cloning the repository and
running the
setup.sh
script. I created the software requirementsdocument to list the software that developers need to install in their
development environments in order to contribute to the product.
I created CONTRIBUTING.md with instructions on how to contribute to the
product. I added instructions on commit signing,
writing commit messages, and the workflows for bug fixes or implementing
new features.
I created the commitlint GitHub Actions workflow to run commitlint to
validate commit messages for the main branch or pull requests for the
main branch.
My configuration is:
Running
npx commitlint --from HEAD~1 --to HEAD --verbose
succeeds.Expected Behavior
Commitlint should succeed and validate that the commit message is valid.
Affected packages
Possible Solution
No response
Context
No response
commitlint --version
@commitlint/cli@19.2.0
git --version
2.44.0
node --version
20.11.1
The text was updated successfully, but these errors were encountered: