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

Update README.md - Document use of Fine Grained Access Token #227

Merged
merged 1 commit into from
Jul 5, 2023
Merged

Update README.md - Document use of Fine Grained Access Token #227

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,10 @@ The default `GITHUB_TOKEN` token can only be used if you are dispatching the sam
To dispatch to a remote repository you must create a [Personal Access Token (PAT)](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) with the `repo` scope and store it as a secret.
If you will be dispatching to a public repository then you can use the more limited `public_repo` scope.

You can also use a fine grained access token (beta). It needs the following permissions on the target repositories:
- contents: read & write
- metadata: read only (will automatically be selected on the GitHub settings page when selecting the contents permission above)

## Example

Here is an example setting all of the input parameters.
Expand Down