Edit on GitHub docs/en/github.md ↗

GitHub integration

1. What the GitHub App is

LaunchPad works as a GitHub App, not as a personal PAT:

Permissions the App expects (docs/admin.md):

Kind Permission
write Contents, Issues, Pull requests, Commit statuses, Actions, Checks
read Metadata, Members
events issues, pull_request, issue_comment, pull_request_review, pull_request_review_comment, organization

Actions/Checks write is used to publish statuses, checks and re-runs; read access lets a task inspect CI through a read-only token.

2. Webhooks

3. Review behaviour

4. Overriding rules from the repository

The default branch may carry .bot/ files that override review, label, development rules and virtual-computer configuration. Repository files win over built-in defaults and over the administrator's console settings; paths, formats and limits are in upstream docs/rules.md. An organisation can tune one repository without changing control-plane code.

5. Repository automation: modular gates

src/automation/ is "framework + pluggable modules + per-repository config" (docs/automation.md):

6. CI gates and the merge queue

"Onboard gates" introduces the lanes:

Lane When
pr-ready every PR commit: build and basic checks
pr-merge merge gate: inside the merge queue when present; otherwise after merge, re-running pr-ready before expensive checks
daily daily
release triggered by a version tag

The onboarding is not a blind overwrite: an agent examines the existing CI and agrees each lane's commands with a person. After the person previews the added/changed files, the control plane creates the gate PR with the gate job, .github/ci-gates.json, missing scripts/gate/gate.mjs and a tag-triggered release.yml. Existing files are merged according to the plan.

An empty lane's not_applicable does not mean the check passed. The control plane does not publish PyPI, npm packages or images.

7. Releases

See Lifecycle · Releases. In short: annotated tag, track the Release workflow, prepare a draft, a person publishes; a tag is never moved or deleted; no new commits means skip.

8. Rate limits and quota

"Global settings → bot accounts → GitHub request quota" lists the hourly quota per account:

When the quota is exhausted the task waits for the window reset; it does not consume a retry.

9. Identity and authorisation

The core of the model: human authority comes from verifiable GitHub evidence, not from the bot's installation token.