crew: one-click GitHub App setup (manifest flow, prefilled), pick which orgs/repos it can access
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github, rust
调研方向
Start by reading the GitHub integration under Atlas Crew → Settings → GitHub and trace how the current gh login credentials are stored and used. Then map the manifest conversion, webhook setup, installation token, and app installation flows described in the issue to the relevant entry points. Done means users can create and install a scoped GitHub App from Atlas while the existing login remains available.
由索引模型根据 Issue 内容生成。
描述
Problem
Today a crew server reaches GitHub through gh signed in as the crew user (device-code login in Atlas Crew → Settings → GitHub). That is a personal login: the crewmates act as that user, with that user's reach, and choosing which organizations and repos the crew may touch means setting things up by hand on GitHub. Creating a GitHub App by hand for the crew (name, permissions, events, webhook URL, keys) is long and easy to get wrong.
Suggestion: one-click GitHub App, created from Atlas
Use GitHub's App manifest flow so the app is created with everything already filled in:
- In Atlas Crew → Settings → GitHub, a Create GitHub App button, with a choice of owner: my account or one of my organizations.
- Atlas opens GitHub's "create app" page with a manifest that already has the name (e.g.
atlas-crew-<server>), the permissions the crew features need (contents, pull requests, issues, checks/actions read, metadata), the events the GitHub automations use (issue comments, issues, pull requests, PR review comments, check runs/workflow runs, releases) and the webhook URL of the crew server's hook server when it is reachable. The user only confirms on GitHub. - GitHub sends back the code; Atlas converts it (
POST /app-manifests/{code}/conversions) and stores the app id, private key and webhook secret on the crew server, as secrets of the crew (never in a repo, never sent to CodeAtlas). - Atlas then opens the app's Install page, where the user picks which organizations and which repos the app gets access to. Changing that later is one link from Atlas Settings.
- Crewmates use short-lived installation tokens from the app for git and the GitHub API, instead of a personal
ghlogin.
Why
- One click instead of a manual app setup.
- Access is scoped by GitHub itself: the owner picks orgs and repos, and can revoke the app at any time.
- Commits, comments and PRs come from a bot identity (
atlas-crew-<server>[bot]), not from the owner's personal account. - With the webhook set, GitHub automations can fire on events instead of polling every 2 minutes.
The current gh login can stay as the simple option.
- 主要语言
- Rust
- 星标
- 3
- 派生
- 1
- 平均合并
- 9 小时 51 分钟
- 30 天内合并 PR
- 310
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
codeatlasdev/atlas 的其他 Issue
-
type: bug
难度 2/5 1-3 小时 新手友好度 75/100
codeatlasdev/atlas#597 ·
维护者通常 1 天内回复
-
area: ci os: linux type: bug
难度 2/5 1-3 小时 新手友好度 78/100
codeatlasdev/atlas#496 ·
维护者通常 1 天内回复
-
area: ci type: bug
难度 3/5 1-2 天 新手友好度 68/100
codeatlasdev/atlas#596 ·
维护者通常 1 天内回复
-
os: linux type: bug
难度 3/5 1-2 天 新手友好度 68/100
codeatlasdev/atlas#591 ·
维护者通常 1 天内回复
-
area: ci os: windows type: bug
难度 3/5 1-2 天 新手友好度 56/100
codeatlasdev/atlas#550 · 1 条评论 ·
维护者通常 1 天内回复
查看 codeatlasdev/atlas 的全部 Issue
相似的 Issue
-
marketing
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
kinqsradio/orbyn-engineering#729 ·
-
Plans page scenario races Shift+Tab against the plan list being drawn again in Firefox and WebKit未关闭bug
难度 2/5 1-3 小时 新手友好度 83/100
nledford/Ladderback#1091 ·
维护者通常 1 天内回复
-
bug fix packaging ui user-sprint
难度 2/5 1-3 小时 新手友好度 78/100
Vondor/KassenSturz#1197 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复