crew: one-click GitHub App setup (manifest flow, prefilled), pick which orgs/repos it can access
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
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.
- Lenguaje dominante
- Rust
- Estrellas
- 3
- Forks
- 1
- Merge medio
- 9 h 51 min
- PR fusionados (30 d)
- 310
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de codeatlasdev/atlas
-
type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
codeatlasdev/atlas#597 ·
Los mantenedores suelen responder en 1 día
-
area: ci os: linux type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
codeatlasdev/atlas#496 ·
Los mantenedores suelen responder en 1 día
-
area: ci type: bug
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
codeatlasdev/atlas#596 ·
Los mantenedores suelen responder en 1 día
-
os: linux type: bug
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
codeatlasdev/atlas#591 ·
Los mantenedores suelen responder en 1 día
-
flaky: Windows scripts job hits test timeouts (check-dco, i18n runner/translate, check-changed)Abiertoarea: ci os: windows type: bug
Dificultad 3/5 1-2 días Aptitud para principiantes 56/100
codeatlasdev/atlas#550 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de codeatlasdev/atlas
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
tinystream-dev/tinystream#132 ·
-
contract good first issue testing
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Emmyt24/nova-launch#2436 ·
Los mantenedores suelen responder en 1 día