.github/release-drafter.ymlconfiguration file to each repository.
For example, take the following
.github/release-drafter.yml file in a repository:
template: | ## What's Changed $CHANGES
As pull requests are merged, a draft release is kept up-to-date listing the changes, ready to publish when you’re ready.
You can use any of the following variables in your template, and they’ll be substituted when the release is regenerated:
||The markdown list of pull requests that have been merged.|
||The previous releases’s tag.|
You can configure Release Drafter using the following key in your
||Required||The template for the body of the draft release. Use template variables to insert values.|
||Optional||The branches to listen for configuration updates to
Release Drafter also supports Probot Config, if you want to store your configuration files in a central repository.