GitHub Changelog Generator
- Output example
- Features and advantages of this project
- Am I missing some essential feature?
Changelog generation has never been so easy
Fully automate changelog generation - This gem generates change log file based on tags, issues and merged pull requests (and splits them into separate lists according labels) from :octocat: GitHub Issue Tracker.
Since now you don't have to fill your
CHANGELOG.md manually: just run the script, relax and take a cup of :coffee: before your next release! :tada:
What’s the point of a change log?
To make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project.
Why should I care?
Because software tools are for people. If you don’t care, why are you contributing to open source? Surely, there must be a kernel (ha!) of care somewhere in that lovely little brain of yours.
[sudo] gem install github_changelog_generator
- Look at CHANGELOG.md for this project
ActionSheetPicker-3.0/CHANGELOG.md was generated by command:
github_changelog_generator -u skywinder -p ActionSheetPicker-3.0
In general, it looks like this:
- Use milestone to specify in which version bug was fixed #22
- Error when trying to generate log for repo without tags #32
Merged pull requests:
It's really simple!
originrefers to your GitHub repo, just go to your project folder and run:
Or, run this from anywhere:
github_changelog_generator -u github_username -p github_project
This generates a changelog to the
CHANGELOG.md file, with pretty markdown formatting.
github_changelog_generator --help for details.
For more details about params, read the Wiki page: Advanced change log generation examples
In your project root, you can put a params file named
.github_changelog_generator to override default params:
unreleased=false future-release=5.0.0 since-tag=1.0.0
GitHub only allows only 50 unauthenticated requests per hour. Therefore, it's recommended to run this script with authentication by using a token.
- Generate a token here - you only need "repo" scope for private repositories
- Run the script with
--token <your-40-digit-token>; OR
- Set the
CHANGELOG_GITHUB_TOKENenvironment variable to your 40 digit token
- Run the script with
You can set an environment variable by running the following command at the prompt, or by adding it to your shell profile (e.g.,
So, if you got an error like this:
! /Library/Ruby/Gems/2.0.0/gems/github_api-0.12.2/lib/github_api/response/raise_error.rb:14:in `on_complete'
It's time to create this token! (Or, wait an hour for GitHub to reset your unauthenticated request limit.)
Migrating from a manual changelog
Knowing how dedicated you are to your project, you probably haven't been waiting for
github-changelog-generator to keep a changelog.
But you probably don't want your project's open issues and PRs for all past features listed in your historic changelog, either.
--base <your-manual-changelog.md> comes in handy!
This option lets append your old manual changelog to the end of the generated entries.
If you have a
HISTORY.md file in your project, it will automatically be picked as the static historical changelog and appended.
rake? We do, too! So, we've made it even easier for you:
we've provided a
rake task library for your changelog generation.
Just put something like this in your
::. :changelog do |config| config.since_tag = '0.1.14' config.future_release = '0.2.0' end
All command line options can be passed to the
rake task as
config parameters. And since you're naming the
rake task yourself, you can create as many as you want.
Features and advantages of this project
- Generate canonical, neat change log file, followed by basic change log guidelines :gem:
- Optionally generate Unreleased changes (closed issues that have not released yet) :dizzy:
- GitHub Enterprise support via command line options! :factory:
- Flexible format customization:
- Customize issues that should be added to changelog :eight_spoked_asterisk:
- Custom date formats supported (but keep ISO 8601 in mind!) :date:
- Manually specify the version that fixed an issue (for cases when the issue's Closed date doesn't match) by giving the issue's
milestonethe same name as the tag of version :pushpin:
- Automatically exclude specific issues that are irrelevant to your changelog (by default, any issue labeled
Distinguish issues by labels. :mag_right:
- Merged pull requests (all merged pull-requests) :twisted_rightwards_arrows:
- Bug fixes (issues labeled
- Enhancements (issues labeled
- Issues (closed issues with no labels) :non-potable_water:
Manually include or exclude issues by labels :wrench:
Customize lots more! Tweak the changelog to fit your preferences :tophat: (See
github_changelog_generator --helpfor details)
Here is a wikipage list of alternatives that I found. But none satisfied my requirements.
If you know other projects, feel free to edit this Wiki page!
Projects using this library
Here's a wikipage list of projects.
If you've used this project in a live app, please let me know! Nothing makes me happier than seeing someone else take my work and go wild with it.
If you are using
github_changelog_generator to generate your project's changelog, or know of other projects using it, please add it to this list.
Am I missing some essential feature?
Nothing is impossible!
Open an issue and let's make the generator better together!
Bug reports, feature requests, patches, and well-wishes are always welcome. :heavy_exclamation_mark:
- I already use GitHub Releases. Why do I need this?
GitHub Releases is a very good thing. And it's very good practice to maintain it. (Not a lot of people are using it yet!) :congratulations:
BTW: I would like to support GitHub Releases in next releases ;)
I'm not trying to compare the quality of handwritten and auto-generated logs. That said....
An auto-generated changelog really helps, even if you manually fill in the release notes!
When I found a closed bug, it's very useful know which release fixed it.
In this case, you can easily find the issue by # in
- it's not quite as easy to find this in handwritten releases notes
- a generated file saves you the trouble of remembering everything; sometimes people forget to add things to a handwritten file
Ultimately, I think GitHub Releases is ideal for end-users.
CHANGELOG.md lives right in the repository, with its detailed list of changes, which is handy for developers.
Finally, there's nothing wrong with using GitHub Releases alongside
CHANGELOG.md in this combination.
- I received a warning: "GitHub API rate limit exceed" What does this mean?
GitHub limits the number of API requests you can make in an hour. You can make up to 5,000 requests per hour. For unauthenticated requests, the rate limit is only up to 60 requests per hour. Unauthenticated requests are associated with your IP address (not the user making requests).
If you're seeing this warning, please do the following:
- Make sure you're providing an OAuth token, so you're not making requests anonymously. Using an OAuth token increases your hourly request maximum from 60 to 5000.
- If you have a large repo with lots of issues/PRs, you can use
--max-issues NUMto limit the number of issues that are pulled back. For example:
- Create an issue and describe your idea
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Add some feature')
- Publish the branch (
git push origin my-new-feature)
- Create a new Pull Request
- Profit! :white_check_mark:
To test your workflow with changelog generator, you can use test repo
Github Changelog Generator is released under the MIT License.