-
-
Notifications
You must be signed in to change notification settings - Fork 204
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
Running git cliff with --prepend requires '-u' or '-l' to be specified #68
Comments
Hello, thanks for reporting this! It is fixed in 1bacc7f 🐻 |
Nice. Thanks! |
Not sure if this is a bug but if you unset + : GIT_CLIFF_CONFIG: project-rp-npm/cliff.toml
+ : GIT_CLIFF_INCLUDE_PATH: 'project-rp-npm/**'
+ : GIT_CLIFF_TAG_PATTERN: 'project-rp-npm-v[0-9].*'
+ : GIT_CLIFF_IGNORE_TAGS: NOPE
+ : GIT_CLIFF_OUTPUT: ./project-rp-npm/CHANGELOG.LATEST.md
+ : GIT_CLIFF_PREPEND: ./project-rp-npm/CHANGELOG.md
+ : GIT_CLIFF_CONTEXT: ./project-rp-npm/GIT_CLIFF_CONTEXT.json
+ unset GIT_CLIFF_OUTPUT
+ git-cliff --context --output ./project-rp-npm/GIT_CLIFF_CONTEXT.json --bump
ERROR git_cliff > Argument error: `'-u' or '-l' is not specified` |
Not sure what's going on there. Do you mean it doesn't work when you don't set it? |
Yes sorry I included too much data and not enough context. I changed the way I generate and got rid of this error for now. It's for sure somehow bugged but looks like an edge case not worth playing around with for me, for now. |
Describe the bug
Git cliff requires
-u
or-l
flags whencommit range
and--prepend
is used.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Command should run fine with CHANGELOG.md file prepended with the commits.
Running
runs pretty fine but creates a whole new entry deleting recent changelogs which really isn't what I want :(.
System (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: