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
Copy file name to clipboardExpand all lines: README.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,9 +109,10 @@ on:
109
109
- If multiple events happen at the same time, then multiple runs of the workflow will trigger
110
110
111
111
# Permissions for the GITHUB_TOKEN
112
-
[Documentation - Permissions for the GitHub Token](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token)
112
+
[Documentation - Modifying the permissions for the GITHUB_TOKEN](https://docs.github.com/en/actions/tutorials/authenticate-with-github_token#modifying-the-permissions-for-the-github_token)
- Use this if you want to modify the default permissions granted to the `GITHUB_TOKEN`
114
-
- Optional, the default can be set (by an admin) to either a `permissive` preset or a `restricted` preset (more info at the link above)
115
+
- Optional, the default can be set in the repo settings (by an admin) to either a `permissive` preset or a `restricted` preset
115
116
- As a good security practice, you should grant the `GITHUB_TOKEN` the least required access
116
117
- When the `permissions` key is used, all unspecified permissions are set to `none`, with the exception of the `metadata` scope, which always gets `read` access.
117
118
- Supported scopes for `permissions`: workflow-level, job-level
0 commit comments