FIX Use pull_request_target so we have access to secrets #65
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.
As per https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflows-in-forked-repositories
This explains why I saw it working in my own account (PR from my account to my account) but it failed in the org (where the PR came from a fork).
Swapping to
pull_request_target
does elevate the default permissions for the built-in token as per https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_targetWe do explicitly specify the
permissions
key and intentionally keep it empty, so we should be able to access secrets while having a read-only github token.Other things to note:
We're not doing any of those
So this should be robust against changes to the action within the PR that triggers it, unlike when using the
pull_request
event. It's actually keeping our secret safer than if thepull_request
event allowed access to secrets.Note
Two commits here - one to do what I mentioned above and another to update the name of the action and job per comments on the issue.
Issue