Integrations

GitHub + Outcome

GitHub shows what shipped. Outcome shows what it was for. Together, each pull request lands on the goal it served, AI-written work is counted apart from the rest, and weekly delivery speed sits beside the number the work was meant to move.

LiveEngineeringMeasuresWorkWrite-back

What each brings

GitHub brings the facts. Outcome turns them into decisions.

UseFrom GitHubWhat Outcome does with it
Measures
  • Pull requests merged and cycle time, by week
  • Deployment frequency and failed deployments
  • Lead time, where Contents is granted
A goal's number is read on a schedule, with its history.
Work
  • Pull requests, including which ones AI agents wrote
  • Deployments, where you grant them
Placed under the goal it serves, so a goal with nothing behind it shows.
Write-back
  • An issue for Claude or another agent to pick up, from a decided gap
A decision becomes an item in the team's own tool, signed by whoever approved it.
Works well with

GitHub + Atlassian + Cursor team usage + PostHog + Outcome

What it never reads
  • Source code
  • Secrets and Actions variables
  • Repositories you do not grant
  • Changes to anything already in GitHub
Status

Live Engineering

Live In the product today. Preview Working, refined with customers.

Setting it up

Connected in minutes, by an admin.

  1. 01Open

    An owner or admin opens Settings, Integrations, GitHub.

  2. 02Connect

    Install the GitHub app on your organization.

  3. 03Read

    Outcome reads it on the schedule you set, from the first day.

  4. 04Send

    Work goes to GitHub only when a person approves it.

Full setup guide for customers

Where it is used

Connect GitHub and see what it brings in on the first sync.

Also in engineering Atlassian · File import · Sentry · ServiceNow · PagerDuty · Azure DevOps · GitLab · Linear