We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The $CONTRIBUTORS variable seems to be including authors of PRs excluded using exclude-labels. For example:
$CONTRIBUTORS
exclude-labels
Notice that @fatiando-bot isn't included in the changelog but shows up in the contributors list.
@fatiando-bot
With configuration:
# Configuration for the Release Drafter workflow name-template: 'v$NEXT_PATCH_VERSION' tag-template: 'v$NEXT_PATCH_VERSION' change-template: '* $TITLE (#$NUMBER $URL by [@$AUTHOR](https://github.com/$AUTHOR))' categories: - title: 'New functions/classes' label: 'feature' - title: 'Enhancements' label: 'enhancement' - title: 'Bug Fixes' label: 'bug' - title: 'Deprecations' label: 'deprecation' - title: 'Documentation' label: 'documentation' - title: 'Maintenance' label: 'maintenance' exclude-labels: - 'skip-changelog' template: | [![DOI](https://zenodo.org/badge/DOI/PASTE_DOI_HERE.svg)](https://doi.org/PASTE_DOI_HERE) ## Highlights * DELETE IF THERE ARE NO HIGHLIGHTS $CHANGES This release contains contributions from: $CONTRIBUTORS
Note: this is the same code and example from #593 but I thought it would be best to open another issue since it's a separate problem.
The text was updated successfully, but these errors were encountered:
duplicate of #569
Sorry, something went wrong.
No branches or pull requests
The
$CONTRIBUTORS
variable seems to be including authors of PRs excluded usingexclude-labels
. For example:Notice that
@fatiando-bot
isn't included in the changelog but shows up in the contributors list.With configuration:
Note: this is the same code and example from #593 but I thought it would be best to open another issue since it's a separate problem.
The text was updated successfully, but these errors were encountered: