[chore] Use pull_request_target event to trigger "add codeowners" workflow
#16228
Conversation
This file contains 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
dmitryax
approved these changes
Nov 9, 2022
mx-psi
approved these changes
Nov 10, 2022
shalper2
pushed a commit
to shalper2/opentelemetry-collector-contrib
that referenced
this pull request
Dec 6, 2022
…orkflow (open-telemetry#16228) Use `pull_request_target` event to trigger "add codeowners to PR" workflow Co-authored-by: Evan Bradley <evan-bradley@users.noreply.github.com>
Closed
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:
This updates the workflow to use the
pull_request_targetevent instead of thepull_requestevent. The former event generates an access token with write permissions on the target repo, as where the latter only creates one with read permissions.I had only tested this on pull requests within my fork, which is why
pull_requestworked in that case. The "auto assign" workflow usespull_request_target, so this should fix the issue.