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
in my case, in gh-actions manually called cz ch like this, as example:
cz ch
cz changelog --dry-run 0.2.0a2 > CHANGELOG.txt
and use as body for gh-release .
Example:
$ git tag v0.1.0 v0.2.0-a0 v0.2.0-a1 v0.2.0-a2
for the prerelease case, I use the current tag, like "0.2.0a2", that's fine.
but for release after all pre-releases i need to collect all commits between releases message like 0.2.0a0..0.2.0
0.2.0a0..0.2.0
at the moment it looks like this
$ cz ch 0.2.0a0..0.2.0 --dry-run ## v0.2.0 (2023-03-13) ### Fix - foo fix 3 ## v0.2.0b0 (2023-03-13) ## v0.2.0a1 (2023-03-13) ### Fix - some fix ## v0.2.0a0 (2023-03-13) ### Feat - super feature ## v0.1.0 (2023-03-13)
I'm thinking about adding a flag for the merged prerelease commit in one release. For example, --merge-prerelease
--merge-prerelease
I want something like this:
$ cz ch 0.2.0a0..0.2.0 --dry-run --merge-prerelease ## v0.2.0 (2023-03-13) ### Fix - foo fix 3 - some fix ### Feat - super feature
In the case of a multi-release range 0.1.0..0.3.0, the output would be:
0.1.0..0.3.0
$ cz ch 0.1.0..0.3.0 --dry-run --merge-prerelease ## v0.3.0 (2023-03-13) ### Fix - foo fix 3 - some fix ### Feat - super feature ## v0.2.0 (2023-03-13) ### Feat - feature ## v0.1.0 (2023-03-13) ### Feat - feature foo
This feature useful for gh-actions for me
- name: Check version uses: apkawa/gh-action-semver-check@master id: version - name: Generate Changelog run: | cz changelog --dry-run ${{ steps.version.outputs.full_with_prefix }}a0..${{ steps.version.outputs.full_with_prefix }} > ${{ github.workspace }}-CHANGELOG.txt - name: Publish archives and packages uses: softprops/action-gh-release@v1 if: ${{ !github.event.schedule && startsWith(github.ref, 'refs/tags') }} with: draft: true prerelease: ${{ needs.version.outputs.prerelease }} body_path: ${{ github.workspace }}-CHANGELOG.txt
In addition, you may need a special syntax for the range Instead of 0.2.0a0..0.2.0 there will be, for example, ~0.2.0. This will make things easier
~0.2.0
#364
The text was updated successfully, but these errors were encountered:
What do you think about this? I'm thinking of making a pull request with this feature.
Sorry, something went wrong.
I think is a good idea. One question though: do we want to merge-prereleases, or skip empty ones? What do you think would make more sense?
I think maybe separate flags
--skip-empty-prerelease
Flag has been added. https://commitizen-tools.github.io/commitizen/changelog/#merge-prerelease
No branches or pull requests
Description
in my case, in gh-actions manually called
cz ch
like this, as example:and use as body for gh-release .
Example:
for the prerelease case, I use the current tag, like "0.2.0a2", that's fine.
but for release after all pre-releases i need to collect all commits between releases message like
0.2.0a0..0.2.0
at the moment it looks like this
Possible Solution
I'm thinking about adding a flag for the merged prerelease commit in one release.
For example,
--merge-prerelease
I want something like this:
In the case of a multi-release range
0.1.0..0.3.0
, the output would be:Additional context
This feature useful for gh-actions for me
In addition, you may need a special syntax for the range
Instead of
0.2.0a0..0.2.0
there will be, for example,~0.2.0
. This will make things easierAdditional context
#364
The text was updated successfully, but these errors were encountered: