Support updating release plan when labels are changed on previously-merged PRs #123
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.
Using the
pull_request
event to trigger the workflow when labels are added on PRs from forks runs into permissions issues when the workflow attempts to open or update the release plan PR. This is because PR workflows from forks do not get repo secrets.The
pull_request_target
event allows triggering a workflow upon an event on a PR from a fork but does include the secrets. It is not safe to run code from the PR in this workflow and the workflow that runs is from the base branch. Since this workflow only pulls the primary branch, this is safe to use. See https://securitylab.github.com/research/github-actions-preventing-pwn-requests/This can be seen working here:
kategengler/test-rp-new#1
Action that ran when the label was changed on the PR https://github.com/kategengler/test-rp-new/actions/runs/9684295098