Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No need to request escalated permissions for GITHUB_TOKEN #357

Merged
merged 1 commit into from May 17, 2023
Merged

No need to request escalated permissions for GITHUB_TOKEN #357

merged 1 commit into from May 17, 2023

Commits on May 17, 2023

  1. No need to request escalated permissions for GITHUB_TOKEN 

    Several of these job steps that use `GITHUB_TOKEN` are read-only
operations, so they don't need elevated permissions for the
`GITHUB_TOKEN`.

And the jobs that _do_ need elevated permissions we're already using a
PAT, so it's not even using the `GITHUB_TOKEN`.

So no need for any custom permissions on the `GITHUB_TOKEN` at all.
    @jeffwidman
    jeffwidman committed May 17, 2023
    Copy the full SHA
    d9fb896 View commit details
    Browse the repository at this point in the history