crew: one-click GitHub App setup (manifest flow, prefilled), pick which orgs/repos it can access

オープン
#528 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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 の本文から書いたものです。

説明

area: desktop status: needs-triage type: feature

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:

  1. In Atlas Crew → Settings → GitHub, a Create GitHub App button, with a choice of owner: my account or one of my organizations.
  2. 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.
  3. 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).
  4. 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.
  5. Crewmates use short-lived installation tokens from the app for git and the GitHub API, instead of a personal gh login.

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分
マージ済み PR(30日)
310

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

codeatlasdev/atlas のほかの issue

codeatlasdev/atlas の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。