Skip to content
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

Replace drafter workflow with github's simple generator config #2887

Merged
merged 1 commit into from
Jan 13, 2022

Conversation

simonbasle
Copy link
Member

This commit replaces the slightly overcomplicated release-drafter
workflow with a simple configuration that will let GitHub's own release
note generator categorize PRs.

GitHub generator doesn't allow to define an overall template for the
notes, nor does it allow customization of how each PR entry looks like.

That said, it is good enough in most cases and seems to deal correctly
with multiple release branches (when fetching and comparing against the
latest tag, it filters on the specified target branch for the release
draft).

The old workflow was more configurable, but also relying on more moving
pieces:

  • a specific Gradle task to compute the latest tag
  • the changelog generating action with non-default fromTag and toTag
    configuration
  • an action requiring a large scope (contents:write) just to be able to
    produce a drafted release

This solution is more limited, but also easier to reason about in terms
of security.

This commit replaces the slightly overcomplicated release-drafter
workflow with a simple configuration that will let GitHub's own release
note generator categorize PRs.

GitHub generator doesn't allow to define an overall template for the
notes, nor does it allow customization of how each PR entry looks like.

That said, it is good enough in most cases and seems to deal correctly
with multiple release branches (when fetching and comparing against the
latest tag, it filters on the specified target branch for the release
draft).

The old workflow was more configurable, but also relying on more moving
pieces:
 - a specific Gradle task to compute the latest tag
 - the changelog generating action with non-default fromTag and toTag
 configuration
 - an action requiring a large scope (contents:write) just to be able to
 produce a drafted release

This solution is more limited, but also easier to reason about in terms
of security.
@simonbasle simonbasle requested a review from a team as a code owner January 13, 2022 14:21
@simonbasle simonbasle added this to the 3.4.15 milestone Jan 13, 2022
@simonbasle simonbasle added the type/chores A task not related to code (build, formatting, process, ...) label Jan 13, 2022
@simonbasle simonbasle self-assigned this Jan 13, 2022
@simonbasle simonbasle requested review from violetagg and a team January 13, 2022 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/chores A task not related to code (build, formatting, process, ...)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants