Skip to main content

Source Control

Source Control integrations connect AI Expedite to your code host, so agents can read repositories, open PRs, watch CI, and respond to webhook events. GitHub is the only source-control provider today; this page documents what's there and where it shows up.

📷 Screenshot: GitHub integration row on Settings → Integrations.

GitHub​

The deepest of any integration in AI Expedite — every Ship-pillar surface (Code, Tests, Deployments, Monitoring) reads from GitHub, and the platform's agents open PRs back into it.

What it unlocks​

  • The Code page — every tab on /<workspace>/code (ChangeLog, Codebase, Tests, Deployments, Monitoring) needs a connected GitHub repo to render content. Without it, the page shows the inline setup flow.
  • Agent-driven PRs — the Code agents that implement Roadmap features open their PRs against your branches via this connection.
  • Webhook events — pushes, PR opens, review requests, check runs, and merge events flow into Inbox under the GitHub category. The code.github-push system hook is the agent that classifies each commit and writes the entry that shows up on Code → ChangeLog.
  • Rate-limit awareness — operations are wrapped in token-bucket rate limiting so a busy workspace can't blow GitHub's per-token quota; failed requests retry with exponential backoff.

Connecting​

Two paths converge:

  • From Code — visiting Code with no repos prompts an inline Install GitHub App button that walks the standard handshake.
  • From Settings → Integrations — the GitHub row exposes the same install + repo-selection flow.

The flow installs the AI Expedite GitHub App into the GitHub org or user account you choose, then asks you to pick which repositories the workspace can see. You can edit that selection later from the same Settings → Integrations row, or from https://github.com/apps/aiexpedite/installations directly.

Scopes​

The app requests:

  • Repository contents (read+write) — needed to clone, read files, and push branches.
  • Pull requests (read+write) — needed to open / update / merge.
  • Issues (read+write) — needed for two-way sync with Issue Trackers when GitHub Issues is the tracker.
  • Actions / checks (read) — needed to surface CI status on Deployments.
  • Webhooks (read) — needed to react to events.

Per-repo selection narrows where these scopes apply — the app can be installed in an org but limited to three specific repos.

Reconnecting​

If the install gets revoked (someone uninstalls the app, the token rotates, the org admin changes policy), an in-page banner on Code surfaces a Reconnect action that drops you back into the same install flow. The connection is restored without losing prior agent context — past PRs, ChangeLog entries, and execution links keep resolving.

Other source-control providers​

GitLab and Bitbucket adapters aren't in the platform yet. The repository abstraction is provider-agnostic so they're additive when they ship — your existing agents won't need to change.