← Documentation
GitHub Integration

Connect Sprintra to GitHub

Install the Sprintra GitHub App once. From then on, every pull request that mentions a Sprintra ticket auto-links to the story, and story statuses move automatically as PRs open, merge, or close. Setup takes under two minutes.

What it does

  • Detects when a PR opens, gets reviewed, or merges in any connected repo.
  • Reads the PR's title, body, and branch name. If it finds a Sprintra ticket reference, links the PR to that story.
  • Moves the linked story status automatically: PR opened → in progress, PR merged → done, PR closed unmerged → back to todo.
  • Captures CI/CD status, code review activity, and deployment events. (DORA dashboard arriving in v1.5.)
  • Permissions are read-only: pull requests, checks, deployments, metadata. Sprintra cannot write to your repos today.

Step 1 — Install the App

From your Sprintra workspace, click Connect GitHub on any project's GitHub settings page. Or visit the install page directly:

https://github.com/apps/sprintra-io

Click Install, sign in with your GitHub account if prompted, and pick which account or organization to install on.

Step 2 — Grant repository access

GitHub will ask which repositories Sprintra can read. Two options:

  • Only select repositories — pick specific repos. New repos you create later are NOT auto-included. Recommended for control.
  • All repositories — every current and future repo on the account. Convenient, less explicit.

Sprintra needs at least one repository in scope before any webhooks fire. GitHub doesn't backfill events for repos added after a PR was opened, so add your repos before opening the PRs you want auto-linked.

Step 3 — Open a PR that references a Sprintra story

Mention your story's ticket key in the PR title, body, or branch name. Any of these formats works:

# Branch name
git checkout -b PROJ-42-fix-login-redirect

# Or in the PR title
Fix login redirect (PROJ-42)

# Or in the PR body
Closes PROJ-42

Within seconds of opening the PR, the story moves to in progress. When you merge, it moves to done. You can see the link on the story's detail page and under Settings → GitHub → Recent Pull Requests.

Multiple repos and projects?

Sprintra routes PRs to projects by ticket key, not by repo. A PR in myorg/web that mentions WEB-42 links to the Web project; the same PR mentioning API-7 instead links to the API project. Monorepos and cross-project PRs work the same way.

Full walkthrough of the routing model and three multi-repo patterns: GitHub integration — routing.

Troubleshooting

My PR didn't link to the story.

Check the PR title, body, and branch name for the ticket key. Sprintra only links when it finds a match. If the ticket exists in Sprintra but the PR is in a repo Sprintra wasn't granted access to, no webhook fires — add that repo to the App's repository access list at github.com/settings/installations.

The story didn't move to In Progress when I opened the PR.

PR Automation Rules only fire on the original open event. If you opened a PR before installing the App or before adding the repo, GitHub doesn't backfill. Close and reopen the PR to trigger a fresh event — or rely on the merge event to move the story to Done.

I want PRs without ticket IDs to still route somewhere.

Today, PRs without a recognizable ticket reference appear under Unlinked PRs in the dashboard but don't auto-move any story. Default routing for ticketless PRs is on the roadmap.

I need to manually link or unlink a PR.

Open the story's detail page. The PR section has a manual-link control for admins.

Next steps