Integrations
Connect GitHub and GitLab so branches, commits, pull requests, merge requests, and pipelines show up on the issues they reference.
On this page
What the integrations do
Source-control integrations sync development activity onto your issues. Map a repository to a Runboard project, and branches, commits, pull requests, merge requests, and pipelines that reference an issue key appear on that issue as a Development section.
Note
Runboard stays the source of truth for issues. These integrations add development context — they don't import GitHub or GitLab issues.
Connecting an account
Under Settings → Integrations, connect GitHub (by installing the Runboard GitHub App on your repositories) or GitLab (by authorizing access). Connecting and managing integrations needs the admin role.
Note
If a provider's Connect button is unavailable, that provider hasn't been set up yet — ask a workspace admin.
Mapping repositories
Once connected, refresh the repository list, map each repo to a project, and turn on Sync events. From then on, activity in that repository is matched to issues in the mapped project.
Development on the issue
Runboard finds issue keys in branch names, commit messages, and pull/merge request titles — so a branch like RUN-12-fix-login links itself to RUN-12. The Development section lists each reference with its kind and a live state badge:
| Reference | States you'll see |
|---|---|
| Branch · Commit | — |
| Pull request · Merge request | open, merged, closed |
| Pipeline · Check | success, failure, pending, canceled |
Improve this article
Spot something missing, outdated, or a broken link? Send the docs team a note.