Replies: 2 comments
-
Hello! 👋🏼 To generate a changelog for the specific part of the Git history, you can use ranges like so: git cliff v2.29.0...main See the other examples here: https://git-cliff.org/docs/usage/examples That being said, I'm not sure if I understood your use case fully. Posting snippets from your Git history, git-cliff configuration and sharing what you want your changelog to look like would really help here :) |
Beta Was this translation helpful? Give feedback.
-
thanks.. was hoping not to specify range.. our master is master but this fails either way
branch list
log
existing changelog , prev release to now
|
Beta Was this translation helpful? Give feedback.
-
we create a release every quarter. our current manual changelog (as part of the PR) gets in the way during the quarter with PR's processed out of date order and creating conflicts.
SO, want to use git-cliff to create the changelog at release time
we create the tag ON the RELEASE... so promote from develop to master, update a couple files on master, tag master
update develop with new proposed release number (package.json)
start updates on develop again, til next release
no parms gives me all the way back to 2016 open of repo
--latest gives me all the changes IN the last tag.. not since
--tag v2.29.0 replicates --latest
sitting in the working directory on the develop branch,
git tag shows the list of tags, (giving the tag regex pattern doesn't help)
git log shows me the commits
what am I doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions