You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For open source projects, the most common way to contribute code is to fork the repo and PR from the fork. This results in the secret.GITHUB_TOKEN passed to this action for pull_request events to have read-only permissions preventing labels from being applied to the PR.
The pull_request_target provides a safe alternative for triggering actions from PRs by running in the context of the base repo rather than the fork. This prevents potentially malicious code from being executed (unless the maintainers don't follow best practices when using this event type). It also provides a secret.GITHUB_TOKEN with write access to the base repo even for PRs from forks.
Currently when trying to use pull_request_target as a trigger for the action, it does not do anything.
The text was updated successfully, but these errors were encountered:
Having this issue as well.
Bit of a shot in the dark, since I don't know much about release drafter (and actions in general), but I would think that it is just a matter of adding
For open source projects, the most common way to contribute code is to fork the repo and PR from the fork. This results in the
secret.GITHUB_TOKEN
passed to this action forpull_request
events to have read-only permissions preventing labels from being applied to the PR.The pull_request_target provides a safe alternative for triggering actions from PRs by running in the context of the base repo rather than the fork. This prevents potentially malicious code from being executed (unless the maintainers don't follow best practices when using this event type). It also provides a
secret.GITHUB_TOKEN
with write access to the base repo even for PRs from forks.Currently when trying to use
pull_request_target
as a trigger for the action, it does not do anything.The text was updated successfully, but these errors were encountered: