Skip to content
Lithora
Lithora Docs

GitHub PR & CI Sync

Connect a repository and Lithora keeps engineering and planning in lockstep — PRs link to work items, CI status shows on the task, and merges move the work to Done.

GitHub sync
MR
ENG-412·To Do

Add autosave to the editor

PR #412·feat/autosaveopen
buildqueued
testsqueued
lintqueued
1 approval

Status updates as the PR and its checks move on GitHub.

Live PR and CI state on the task card — checks resolve, the PR badge moves open → merged, and the task advances automatically.

What syncs

  • Issues, both ways: Push a Lithora work item to GitHub as an issue, and let inbound webhooks reflect issue opens, closes, and reopens back onto the work item. Lithora can also create, comment on, label, and close issues on your behalf.
  • Linked pull requests: Use a GitHub closing keyword in the PR title or body — Closes #12, Fixes #12 — and the PR links to whichever Lithora work item is tied to issue #12 in that repo. That is the mechanism behind the status automation below, so if a PR is not moving a task, check the closing keyword first.
  • CI check rows: Each CI check (build, tests, lint) shows live on the task card and updates as the run progresses.
  • Status on merge: Opening a PR can move a task to In Review; merging it completes the task — no manual status updates.

Code-aware AI (optional)

With a repo connected, the AI agent can use code context. These run only when you enable them per repository — they are off by default.

PR review

The agent reviews an opened PR and posts findings.

Code-aware decomposition

Break an issue into subtasks informed by the actual codebase.

CI-failure triage

On a failed run, the agent stages a triage plan for your approval.

PR review quota

AI PR reviews draw from a monthly allowance that is granted per seat and pooled across the org: 5 reviews per seat on Pro and 15 per seat on Scale. One review is one pull request — re-reviews after a push are included. The allowance resets monthly and does not roll over. Webhook-triggered runs stage a gated plan you approve before anything is changed.

Connecting a repository

  1. Go to Dashboard → GitHub (or Dashboard → Integrations).
  2. Authorize Lithora for the repositories you want to connect.
  3. Choose per-repo settings — link-only sync, or enable the code-aware AI features.
  4. Optionally import an existing backlog: Sync now on the GitHub card opens the import dialog so you can pick a repository and bring its issues in as work items.

GitHub connects on any plan

Unlike the other providers, GitHub has no plan gate on connecting — link a repo and get issue and PR sync straight away. The AI layers on top of it (PR review, code-aware decomposition, CI triage) consume your plan's AI allowances, so those need an active Pro or Scale subscription or trial. See Integrations for the full provider list.