Repository navigation
Release workflow example uses regular pull request events - #114
Draft
Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
Draft
Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
Marius Storhaug (MariusStorhaug) wants to merge 1 commit into
Conversation
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.
The README release workflow example now uses
pull_requestinstead ofpull_request_target. This matches the repository workflows. The action code and existing consumer workflows do not change.Fixed: Release workflow example uses regular pull request events
Users who copy the example now configure regular pull request events. The branch filter and event types stay the same. No action is required for existing consumers unless they want to adopt the updated example. To adopt it, replace
pull_request_targetwithpull_requestin the calling workflow.For pull requests from forks,
GITHUB_TOKENis read-only by default. Release creation and pull request comments require write permissions, so those operations can fail on fork runs. This documentation change does not add support for privileged fork runs.Technical details
pull_request.pull_request_targetreferences remain in the repository.git diff --checkpassed.750abed0ecab02394554b610dc3aa191e75e3248to candidate6660fe91979ce1cd3f08d0c6c746ab951a83f2ec.action.ymlandsrc/**. This README-only change does not invoke that release route.PSModule/Release-GHRepository; none is fully resolved by this one-line change.