Conversation
Contributor
|
Preview deployment: https://gha-post-release.preview.avy-fx.org |
Contributor
|
🚀 This is included in version v1.8.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a GitHub Actions workflow that automatically comments on issues and PRs when a release includes their fix, so contributors and reporters know which version contains their change.
Related Issues
Fixes #938
Key Changes
.github/workflows/post-release.ymltriggered onrelease: publishedeventsapexskier/github-release-commenter@v1to scan commits between releases and comment on associated issues/PRsWhy
apexskier/github-release-commenterinstead of Payload's fork?This workflow was originally copied from Payload's
post-release.yml, which uses a custom composite action (.github/actions/release-commenter) — a fork of the apexskier action with modifications for Payload's monorepo release process (tag filtering for non-linear multi-package releases, commenting on locked issues). Those features aren't relevant to us, and using the published action avoids maintaining a vendored copy of their fork.How to test
Future enhancements / Questions
label-templateto automatically label released issues (e.g.,released)skip-labelto exclude certain issues (e.g., dependency bumps) from being commented on