github / github/accessibility-scanner

2. Create a token and add a secret - CLARIFICATION

Open
#119 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
369
Forks
40
Avg merge
1d 9h
Merged PRs (30d)
10

Description

We need a [GH_TOKEN is a fine-grained PAT](https://github.com/marketplace/actions/accessibility-scanner#2-create-a-token-and-add-a-secret) with:

```
actions: write
contents: write
issues: write
pull-requests: write
metadata: read
```

So
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#pre-filling-fine-grained-personal-access-token-details-using-url-parameters

We can pre-fill and not use:

```
https://github.com/settings/personal-access-tokens/new
?name=Repo-reading+token
&description=Just+contents:read
&target_name=octodemo
&expires_in=45
&contents=read
```

But maybe a [link like this](https://github.com/settings/personal-access-tokens/new?name=Accessibility-scan+token&description=GitHub+A11y+Scanner&actions=write&contents=write&issues=write&pull_requests=write&metadata=read):

```
https://github.com/settings/personal-access-tokens/new
?name=Accessibility-scan+token
&description=GitHub+A11y+Scanner
&actions=write
&contents=write
&issues=write
&pull_requests=write
&metadata=read
```

Correct?

Contributor guide

Open the contributing guide

Research direction

Review the linked Marketplace setup instructions and GitHub fine-grained personal access token documentation first. Confirm whether the listed permissions and pre-filled URL are correct, then update the token-creation guidance so it clearly specifies the required scopes and valid link.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
documentation, security
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.