We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Not really. The OSSF GitHub Action Issue states if we use a ruleset instead of a branch protection we can use the base/given GH_TOKEN instead of a custom PAT that needs additional permissions.
GH_TOKEN
We should also use GitHub's newer tooling on our repositories to be an example of usage.
Migrate from branch protection rule to ruleset
We will want the permissions to initially match 1 to 1.
N/A
The text was updated successfully, but these errors were encountered:
we can use the base/given GH_TOKEN instead of a custom PAT
Oh cool!
Sorry, something went wrong.
@ajhenry will need your help on ICF to do this since I don't have permissions.
This has been completed.
No branches or pull requests
Is your feature request related to a problem?
Not really. The OSSF GitHub Action Issue states if we use a ruleset instead of a branch protection we can use the base/given
GH_TOKEN
instead of a custom PAT that needs additional permissions.We should also use GitHub's newer tooling on our repositories to be an example of usage.
Related OSPO Tool
Describe the solution you'd like
Migrate from branch protection rule to ruleset
We will want the permissions to initially match 1 to 1.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: