32 lines
987 B
Markdown
32 lines
987 B
Markdown
You can define the access that the `GITHUB_TOKEN` will permit by specifying `read`, `write`, or `none` as the value of the available scopes within the `permissions` key.
|
|
|
|
```yaml
|
|
permissions:
|
|
actions: read|write|none
|
|
checks: read|write|none
|
|
contents: read|write|none
|
|
deployments: read|write|none{% ifversion fpt or ghec %}
|
|
id-token: read|write|none{% endif %}
|
|
issues: read|write|none
|
|
discussions: read|write|none
|
|
packages: read|write|none
|
|
pages: read|write|none
|
|
pull-requests: read|write|none
|
|
repository-projects: read|write|none
|
|
security-events: read|write|none
|
|
statuses: read|write|none
|
|
```
|
|
|
|
If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
|
|
|
|
You can use the following syntax to define read or write access for all of the available scopes:
|
|
|
|
```yaml
|
|
permissions: read-all|write-all
|
|
```
|
|
|
|
You can use the following syntax to disable permissions for all of the available scopes:
|
|
|
|
```yaml
|
|
permissions: {}
|
|
``` |