-
Notifications
You must be signed in to change notification settings - Fork 141
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
Incremental changelog #26
Comments
@farcepest has a branch on start/end. Putting the commit refs here for later reference. |
This is indeed a very useful feature to have as I already have existing changlog files. Also, related to support existing changlog files, it would be nice to be able to customize the way each section is generated, for e.g. I don't use RST section for labels (i.e. New, Fix, Changes), I just want them to be a list and related commits are their list items. |
Ok, thanks for your feedback, note that sectioning concern is also marked in the missing feature in #21 with some workaround if this can help in the meantime. |
…l changelog output (fixes #26) See use cases documentations for more information.
I've just committed a branch
Please look at additions in Many thanks for your interests. |
Thanks for the update, will test it with my setup. Is it possible to have something like:
Basically I would like to output the changelog relative to the current HEAD. Perhaps the command that I would use the most is |
Well, unless I've misunderstood, this is already working.
is equivalent (for compatibility with legacy) to call:
which is equivalent (by design) to call:
Which shows the complete changelog. You are maybe interested by having only the last changes (since your last tag to HEAD). Which you can do by issuing
As a start, I figured that these question could be answered externally from I'm open to include a way to figure these out internally now, but it must provide maximum configurability. An option in the taste of |
Sorry what I actually meant was: is there a way to quickly generate a changelog for the latest version (could be the last tag, HEAD or HEAD^ etc.) without specifying the exact tags? I believe that's what most people would want when releasing a new version. So running:
should be equivalent to running one of the following: # the latest version is unversioned (not tagged yet)
# get changelog from last stable version up to HEAD
gitchangelog show STABLE...HEAD
# or it is already tagged, get changelog from last previous version to the last stable version
gitchangelog show STABLE^...STABLE I hope that makes sense, but not sure if doable at all. |
@kminh: I'll head toward a release of the previous feature, even if I read your last message and I acknowledge it doesn't fullfill all your requirements. I'll create another issue to track the progress of the last part as I understood it.
|
For several reason, building changelog incrementally is sometimes required, usually when you want to commit your CHANGELOG:
gitchangelog
, or change your conventions:This would require
gitchangelog
to accept somerev-list
type of argument, with optional detection of last revision made, and/or automatically insert in a file. This could be all driven by options in the config file, or command line arguments.The text was updated successfully, but these errors were encountered: