Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Produce changelog with cz bump --dry-run --changelog-to-stdout #538

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

Closed
bavedarnow opened this issue Jul 26, 2022 · 2 comments · Fixed by #539
Closed

Produce changelog with cz bump --dry-run --changelog-to-stdout #538

bavedarnow opened this issue Jul 26, 2022 · 2 comments · Fixed by #539

Comments

@bavedarnow
Copy link
Contributor

bavedarnow commented Jul 26, 2022

Description

I'm using the commitizen pre-commit hook paired with renovate for automated dependency updates.

I'd like to test the commitizen functionality before merging the upgrade PR. One thing I'd like to see is if the changelog is being generated correctly.

Issue:

pairing the --dry-run arg with --changelog-to-stdout does not produce the changelog

Steps to reproduce

  1. checkout your repository at an older version tag git checkout 1.0.0
  2. soft reset to a newer version git reset --soft 1.1.0
  3. cz bump --changelog-to-stdout --dry-run

not sure if this matters, but changelog_incremental = true

Current behavior

cz bump --changelog-to-stdout --dry-run
bump: version 1.0.0 → 1.1.0
tag to create: 1.1.0
increment detected: MINOR

Desired behavior

cz bump --changelog-to-stdout --dry-run
bump: version 1.0.0 → 1.1.0
tag to create: 1.1.0
increment detected: MINOR

## 1.1.0 (2022-07-25)

### CHANGELOG SHOWS UP HERE

Screenshots

No response

Environment

cz version --report
Commitizen Version: 2.27.1
Python Version: 3.10.4 (main, May 26 2022, 14:56:41) [Clang 13.1.6 (clang-1316.0.21.2.5)]
Operating System: Darwin
@woile
Copy link
Member

woile commented Jul 26, 2022

Seems like a valid bug. I will try to submit a fix soon

bavedarnow pushed a commit to bavedarnow/commitizen that referenced this issue Jul 26, 2022
bavedarnow pushed a commit to bavedarnow/commitizen that referenced this issue Jul 26, 2022
@bavedarnow
Copy link
Contributor Author

Seems like a valid bug. I will try to submit a fix soon

I opened a PR here: #539

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants