1mn.ai docs
Integrations

GitHub

Install the 1mn GitHub App so coding, content, error-triage, and docs loops can read your repo and open pull requests — with short-lived, installation-scoped tokens.

Connect GitHub to let 1mn read your repository and open pull requests. It's required for every loop that writes code or docs — coding tasks, the content writer, error triage, and the docs loop all clone your repo, push a branch, and open a PR you review.

1mn connects through a GitHub App installation, not a personal access token. It never stores a long-lived credential: it persists only the installation id and the repo you select, then mints a short-lived installation access token (~1 hour TTL) on demand for each clone, push, or API call.

Prerequisites

  • A GitHub account or organization that owns the repository you want the agent to work in.
  • Permission to install a GitHub App on that account (org owners may need to approve it).

Connect GitHub

  1. Open Integrations (/dashboard/integrations) and find the GitHub (coding tasks) card.
  2. Click Connect GitHub. This sends you to GitHub's app-install screen (github.com/apps/<app>/installations/new).
  3. Choose the account, then select which repositories the app may access — pick only the repos you want the agent to touch.
  4. Approve. GitHub redirects you back and the card shows the connected account.
  5. If more than one repo is available, use Change repository to set the active repo for this product — loops that need a repo use this selection.

The app requests these repository permissions:

  • Contents — Read & write (clone branches, push commits)
  • Pull requests — Read & write (open the PR for you to review)
  • Metadata — Read-only (required by GitHub for any app)

Manage or switch repositories

  • Change repository — pick a different active repo from the ones the installation can see.
  • Manage repositories — returns to GitHub's installation settings to add or remove repos from the app.
  • Disconnect — removes the connection for this product. Coding and docs tasks stop until you reconnect; your code is untouched.

Example: what a coding task does with the connection

Once GitHub is connected, a coding task runs entirely against tokens minted on demand — you never paste or handle a token:

# Inside the sandbox, git is pre-authenticated with a short-lived token:
git clone https://github.com/<owner>/<repo>.git repo
cd repo
git checkout -b adagent/<change>
# … the agent edits files …
git commit -am "feat: <change>"
git push origin adagent/<change>
# 1mn then opens a pull request linked to the ticket for you to review.

The result is a pull request on your ticket — nothing merges without your review.

Notes & limits

  • No token to rotate. Because tokens are installation-scoped and expire in about an hour, there's no long-lived secret to leak or rotate. Revoke access any time by uninstalling the app on GitHub or clicking Disconnect.
  • One active repo per product. Loops act on the selected repo; switch it with Change repository.
  • Org approval. On organizations with third-party app restrictions, an owner must approve the 1mn app before installation completes.

On this page