Use pull_request_target
trigger in release workflow
#2007
Merged
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
The new
release
workflow is not triggered automatically after merging the changes frompre-release
.This happens because I used the wrong trigger:
pull_request
does not have access to the requiredBOT_TOKEN
to make this operation.We need to use
pull_request_target
for that as it was described in the GitHub Documentation.The manual
workflow_dispatch
trigger seems to work just right.Motivation and context
How has this been tested?
Examples
Type of change
Checklist
build_docs
label to this pull request (if you don't have enough privileges a reviewer will do it for you)