Skip to content

Commit 8d7ac4a

Browse files
authoredOct 30, 2024··
docs: Update Token permissions in README.md
docs: Update Token permissions in README.md
2 parents 381dd35 + c476011 commit 8d7ac4a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed
 

‎README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -134,9 +134,9 @@ jobs:
134134
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
135135

136136
```
137-
You need to create a secret with write and repo permissions in the repository settings to pass it as `GITHUB_TOKEN` in the workflow. 🔑 **Fine-grained tokens** are preferred, and you need to set repository permissions to obtain:
138-
- **Read** access to actions variables, metadata and secrets.
139-
- **Read** and **Write** access to actions, contents (code), commit statuses, pull requests, and workflows.
137+
You need to create a secret with write repository permissions. You can create a PAT token and add it as a secret in the repository settings (go to `Settings > Secrets and variables > Actions > New repository secret`). In case of setting up a 🔑 **fine-grained token**, you need to set the following repository permissions:
138+
- **Read** access to actions, metadata and secrets.
139+
- **Read** and **Write** access to contents (code).
140140

141141
Also you need to add read and write permissions to workflows in your repository. You can find it under `Settings > Action > General > Workflow permissions`.
142142

0 commit comments

Comments
 (0)
Please sign in to comment.