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

Abierto
#528 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, rust

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
3
Forks
1
Merge medio
9 h 51 min
PR fusionados (30 d)
310

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codeatlasdev/atlas

Todos los issues de codeatlasdev/atlas

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.