GitHub and GitLab

Connect GitHub or GitLab so merge requests and checks appear on Pulse issues.

GitHub and GitLab

Connect Pulse issues to branches, merge requests, and CI checks on GitHub or GitLab — so delivery status lives next to the task.

Connect a provider

Workspace managers configure integrations at:

Settings → Integrations → GitHub or GitLab
(`/settings/integrations/github` | `/settings/integrations/gitlab`)

Complete OAuth or token setup per your organization's policy. Repository access follows grants configured during connection — Pulse only shows development activity for repos you can read.

What appears on issues

On issue detail, the Development section (separate from Resources) shows linked:

  • Pull requests (GitHub) or merge requests (GitLab)
  • Review and check status when the provider reports them
  • Links out to the provider for diffs and logs

Link a branch or MR from issue actions when development linking is enabled for the team repository.

Checks and Reviews

GitHub Actions checks may surface step status on the development card. For a full merge-request inbox, open Reviews when the reviews capability is enabled — Reviews reads connected repos through pulse-agent, while development links on issues show MR/PR status inline.

GitLab vs GitHub

Pulse supports both providers with the same conceptual model:

ProviderLink type
GitHubPull requests, Actions checks
GitLabMerge requests, pipeline status

Self-hosted GitLab uses the same integration flow with your instance URL.

Permissions

Connecting integrations requires workspace manager access. Viewing development links on an issue requires read access to the issue and the linked repository.

Troubleshooting

ProblemWhat to check
Development section emptyNo MR/PR linked yet, or repo not granted
Checks staleProvider webhook or sync delay — refresh from provider
Cannot linkRepository not in connection scope

Next

Last updated on