github / github/accessibility-scanner
2. Create a token and add a secret - CLARIFICATION
- 主要语言
- TypeScript
- 星标
- 369
- 派生
- 40
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 10
描述
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?
贡献指南
调研方向
首先,查看链接的 Marketplace 设置说明和 GitHub fine-grained personal access tokens 文档。确认列出的权限和预填充的 URL 是否正确,然后更新令牌创建指南,明确指定所需的 scopes 和有效链接。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github
- 领域
- documentation, security
- Issue 类型
- 文档
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100