README.adoc

March 26, 2026 ยท View on GitHub

= GitHub Changelog Generator

A changelog generator for GitHub Issues, available as a https://github.com/spring-io/github-changelog-generator/releases[release jar] or for use as a GitHub Action.

== Running as a Release Jar

The changelog generator requires Java 17 or later. To generate a markdown changelog using a https://github.com/spring-io/github-changelog-generator/releases[release jar], follow these steps:

To increase https://developer.github.com/v3/?#rate-limiting[GitHub's rate limits], you can also use --github-token=<token> to provide an access token that is used for authentication.

For more advanced configuration options, <<Advanced Configuration,see below>>.

== Using as a GitHub Action

=== Configuration

==== Required Inputs

  • milestone: Milestone for which the changelog should be generated

=== Optional Inputs

  • changelog-file: Path of the file to which the changelog should be written. Defaults to changelog.md
  • config-file: Path to a changelog generator configuration file, relative to GITHUB_WORKSPACE. <<Advanced Configuration,See below>> for details of the advanced options that can be configured using this file.
  • repository: Repository for which a changelog should be generated. Defaults to the workflow's repository.
  • token: Token for authentication with GitHub. Authenticating increases GitHub rate limits.

=== Minimal Example

[source,yaml,indent=0]

steps:

  • name: Generate Changelog uses: spring-io/github-changelog-generator@ with: milestone: '1.0.0'

== Advanced Configuration

A YAML configuration file can be used to provide more complex configuration, either when running as a release jar or as a GitHub action.

=== Customizing Sections

By default, the changelog will contain the following sections:

|=== |Title |Label Text

|":star: New Features" |"enhancement"

|":lady_beetle: Bug Fixes" |"regression" or "bug"

|":notebook_with_decorative_cover: Documentation" |"documentation"

|":hammer: Dependency Upgrades" |"dependency-upgrade" |===

The title is in https://guides.github.com/features/mastering-markdown[Markdown] format and emoji like ":star:" can be used. If you want something different then you can add sections YAML:

[source,yaml]

changelog: sections:

  • title: "Enhancements" labels: ["new"]
  • title: "Bugs" labels: ["fix"]

By default, adding sections will replace the default sections. To add sections after the defaults, add the following configuration:

[source, yaml]

changelog: add-sections: true

You can also customize the contributors title using the following:

[source,yaml]

changelog: contributors: title: "Contributors"

You can add external links such as release notes for quick access using the following:

[source,yaml]

changelog: external_links:

==== Showing Issues in Multiple Sections

Unless otherwise configured, issues will only appear in the first matching section. For example, if you have an issue labeled with enhancement and documentation then it will only appear in the "New Features" section.

If you want an issue to appear in multiple sections, use the group property. Groups allow you to create logical groupings of related sections. An issue may only appear once in any given group.

For example, you might define the following:

[source,yaml]

changelog: sections:

  • title: "Highlights" labels: ["noteworthy"] group: "highlights"
  • title: "Enhancements" labels: ["new"]
  • title: "Bugs" labels: ["fix"]

This will create two distinct groups, "highlights" and "default" (which is used if no group property is specified). An issue labeled with new and noteworthy will appear in both the "Highlights" and "Enhancements" section.

==== Custom Summaries

By default, an issue's entry in the changelog summarizes the issue using its title. Alternatively, summaries can be derived from a comment made by a member of the issue's owning organization or by applying a regular expression to its body.

===== Member Comment

To be used as the summary, a comment must begin with a configured prefix. The prefix is not included in the summary. When no such comment is found on the issue, the chain of <<_following_ported_issues,ported issues>> is checked and the first matching comment in the chain is used. If no matching comment is found, the issue's title is used as a fallback.

For example, you might define the following:

[source,yaml]

changelog: sections: - title: "Noteworthy Changes" labels: - "status: noteworthy" summary: mode: "member-comment" config: prefix: "Noteworthy change:"

This will create a section entitled "Noteworthy Changes" that will include one entry for each issue labelled with "status: noteworthy". Each entry will use the text from the first member's comment that begins "Noteworthy change:" to summarize the issue. If no such comment is found, the issue's title is used.

===== Body Regex

A summary can be extracted by applying a regex to the body of the issue. If the regex matches, the issue is summarized using its first group. If the regex does not match, the issue's title is used.

For example, you might define the following:

[source,yaml]

changelog: sections: - title: "Dependency Upgrades" sort: "title" labels: - "type: dependency-upgrade" summary: mode: "body-regex" config: expression: '(Upgrade to [.](.)).*'

This will create a section entitled "Dependency Upgrades" that will use the regex (Upgrade to \[.*\]\(.*\)).* to summarize the issue. If the body does not match the regex, the issue's title is used.

=== Excluding Issues

Issues and pull requests can be excluded from the changelog by configuring exclusions. You can ignore all items that have certain labels using changelog.issues.exclude.labels. For example:

[source,yaml]

changelog: issues: exclude: labels: ["wontfix", "question", "duplicate", "invalid"]

=== Excluding Contributors

Contributors whose username ends with [bot], such as dependabot[bot] and github-actions[bot], are automatically excluded. If you have other contributors that you want to be excluded (perhaps core team members), you can set the following:

[source,yaml]

changelog: contributors: exclude: names: ["coremember"]

You can also use * if you want to drop the contributors section entirely.

=== Sorting Issues

By default, issues are sorted by their "created" date. If you want to order them by title instead you can set changelog.issues.sort to title. It's also set the property on section configuration if you want ordering per section:

[source,yaml]

changelog: sections:

  • title: "Bugs" labels: ["bug"]
  • title: "Dependency Upgrades" labels: ["dependency"] sort: "title"

=== Following Ported Issues

If an issue is forward-ported or backward-ported between milestones, you might have separate issues in each milestone that reference the original issue. To allow the changelog generator to find these linked issues, configure the labels that are used to identify ported issues. The body of a ported issue should contain a comment with a reference to the original issue. The reference is extracted using a regular expression with exactly one capture group for the original issue number.

[source,yaml]

changelog: issues: ports: - label: "status: forward-port" bodyExpression: 'Forward port of issue #(\d+).' - label: "status: backport" bodyExpression: 'Back port of issue #(\d+).'

The changelog generator will use the links between ported issues to:

  • Credit a contributor in the changelog for every milestone that includes a forward or backward port of the issue that was resolved
  • Find member comments when looking for a <<_custom_summaries,custom issue summary>>

=== Disabling Generation of Links to Each Issue

By default, each entry in the changelog will include a link back to the issue or PR on GitHub. The generation of these links can be disabled:

[source,yaml]

== License

This project is Open Source software released under the https://www.apache.org/licenses/LICENSE-2.0.html[Apache 2.0 license].