The doc should provide a minimum list of permissions for the GitHub Access Token

未关闭
#2,963 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
57/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
冷清
技术栈
github

调研方向

从 docs/installation-guides/README.md 开始,查看其中链接的 GitHub token 创建页面,以核实服务器文档目前假定了哪些权限。更新指南,明确所需的最低权限,并引导用户使用适当的 token 流程;当设置说明具体明确且最小权限建议清晰时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

enhancement request ai review
Describe the feature or problem you’d like to solve

A clear and concise description of what the feature or problem is.

All installations with Personal Access Tokens (PAT) require: GitHub Personal Access Token (PAT): Create one here

Regardless of which installation method you choose, follow these security guidelines:

Limit Token Scope: Only grant necessary permissions to your GitHub PAT

  • However, the list of permissions for personal access token (classic) is too long. I think the documentation needs to provide a minimum list of required permissions. See https://github.com/settings/tokens/new .
  • Image
  • Furthermore, the URL provided in the documentation is for creating the personal access token (classic). I think the documentation should guide users to use the fine-grained personal access token, which only allows access to repositories within a specific scope, while the personal access token (classic) allows access to all unrelated repositories.
  • Image
Proposed solution

How will it benefit GitHub MCP Server and its users?

  • This would obviously reduce the cognitive load.
Example prompts or workflows (for tools/toolsets only)

If it's a new tool or improvement, share 3–5 example prompts or workflows it would enable. Just enough detail to show the value. Clear, valuable use cases are more likely to get approved.

  • Null.
Additional context

Add any other context like screenshots or mockups are helpful, if applicable.

  • Null.
主要语言
Go
星标
33.1k
派生
5k
平均合并
2 天 15 小时
30 天内合并 PR
27

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/github-mcp-server 的其他 Issue

查看 github/github-mcp-server 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。