GitHub

Link Pulse issues to GitHub pull requests, commits, and checks.

Configure

Only workspace owners and admins can manage integrations. Open Settings → Integrations (/settings/integrations), then GitHub (/settings/integrations/github).

If the card reads Unavailable, this deployment has not configured the public Try Pulse GitHub App. Existing connections stay as they are.

Organization connection

To connect GitHub:

1. Open GitHub in Integrations.
2. Choose Enable. Pulse opens GitHub so you can install the Try Pulse GitHub App on an account or organization.
3. Select the repositories Pulse may access, then return to Pulse.

Connected organizations lists each installation. Connect a new organization adds another. Suspending or uninstalling one never affects another.

Disconnect… removes the connection and repository access from this Pulse workspace. The GitHub App remains installed on GitHub until you uninstall it there. Configure in GitHub opens the installation.

Repository access is the intersection of what GitHub allows and what this workspace grants — it can only ever narrow. Refresh from provider re-reads the installation.

Account connection

A Personal GitHub account is optional and separate from the organization installation. Connect it on this page, or under Settings → Connected accounts (/settings/applications). Revoking one never disables the other.

Use a personal account for actions that must be attributed to you. Organization automation continues under the installation identity without it.

Linking your work

Linked pull requests and commits appear on the issue under Diffs. Empty copy is Link a pull request. Choose Add pull request…, paste a GitHub pull request URL from a connected repository, then pick a link type:

• Closes this issue
• Contributes to this issue
• Related
• References this issue

States include Open, Draft, Merged, and Closed. Checks and review decisions show on the card when GitHub reports them. Overflow actions include Open in GitHub, Refresh from provider, Change link type, and Unlink pull request.

Pull request linking

Pulse reads an issue identifier from automatic sources (on by default):

• Branch name
• Title
• Description

Turn those sources off under GitHub workflow settings if you only want manual links.

Include the identifier in a branch name or pull request so the link is created without pasting a URL. Copy a branch name from an issue with Copy git branch name (Cmd/Ctrl Shift .). Personal branch format lives under Settings → Code & reviews.

Commit linking

Link commits to issues with magic words is off by default. A commit message is rewritten by rebases and cherry-picks, so a link made from one can move. Turn the switch on when you want commit messages to create links.

Magic words

Put a magic word and an issue identifier in a pull request title or description — and in commit messages if that switch is on. For example: Fixes PUL-42 or Part of PUL-42.

Closing phrases such as fix, fixes, close, closes, resolve, and implements mark Closes this issue. Contributing phrases such as part of, ref, references, contributes to, and towards mark Contributes to this issue. related to marks Related. skip or ignore suppresses automatic evidence for that identifier.

A bare identifier without a closing or contributing phrase does not run team status automation.

Issue linkbacks

Linkbacks posts one managed comment on the pull request with a link to the Pulse issue. Default off. Choose Public repositories and Private repositories separately. Include the issue title is off by default: a repository’s readers are not the issue’s readers.

Workflow automation

Issue status automation

Which Pulse status a pull request or commit event moves an issue to is configured per team.

Open Settings → Your teams → <team> → Source control workflow. Automate issue statuses is off by default. Rules are per provider — configure the GitHub column.

Only links that close or contribute to an issue ever automate; a bare mention never does. Merged applies only once every closing change request and commit has landed. Closed without merging never completes an issue.

Events include Draft opened, Opened for review, Ready to merge, Merged, Closed without merging, and more. Do nothing leaves the status unchanged.

Pulse Agent Code Intelligence and coding sessions read granted repositories. Configure those under Settings → AI & Agents. See Pulse Agent.

Target-branch rules

Target-branch rules override the defaults for change requests aimed at particular branches. An exact branch always beats a pattern; among patterns, the one nearest the top wins. Use the default inherits. Preview shows what would happen for a given target branch.

Assign and move forward

Move issue to In Progress on branch copy is a personal switch on Code & reviews, not a GitHub-organization setting.

Reviews

Reviews is the merge-request inbox. It is not the Diffs list on an issue. Enable Reviews under Settings → Features, then connect GitHub here.

FAQ