-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
change log was generated with garbage data #798
Comments
I am experiencing this as well. I think a quick fix is to write |
Have you tried using git_redirect_stderr ? |
@woile, yes, it doesn't seem related. The commitizen/commitizen/changelog.py Line 83 in b8c0c7c
|
We see this with our (old) non-semver tags, as well. Is there a way to specify "ignore tag XYZ" in Thanks. |
Hi all, I just tested with the latest version with |
Description
I extended the
ConventionalCommitsCz
class with my own class that it's whole purpose was to bump patch version for commit with prefixtest(bump): <some title>
.my file cz_bumpForTest.py
and setup.py
the bump actually works well and it's indeed bumps the patch version for the relevant commit.
but the change log looks like this for all type of commits:
there are other repositories that this list of invalid tags is very long.
how to remove it? is the behavior configurable?
EDIT
after going deeper in the code I found the following pr 8123bcb
which I see now the function
get_version_tags
generates this kind of messagesis there a way to override it? or disable this warning?
my repositories has tags that are not semver
Steps to reproduce
I am wrapping the
cz
cli using python codebut eventully I call the command
cz ch --dry-run --start-rev <original_tag> --unreleased-version "<new_tag>"
Current behavior
the release notes contains invalid tags messages
Desired behavior
I dont expect it to add all those invalid tags to the release notes
Screenshots
No response
Environment
I am using the latest versions
The text was updated successfully, but these errors were encountered: