GitHub

Overview

The GitHub integration connects your DevStride organization to GitHub through the DevStride GitHub App. Once it is installed, pull requests are tied to your work items so you can see PR status, reviews, and checks without leaving DevStride.

There are two ways a pull request gets linked to a work item:

• Automatically, when the work item's number appears in the PR's branch name, commit message, title, or description.
• Manually, when you paste a PR's URL into the work item's Github tab — useful for any PR that doesn't reference a work item number anywhere.

Setting up the integration

The GitHub integration is installed at the organization level via the DevStride GitHub App.

1. Open Settings from the bottom of the left-hand sidebar.
2. Select Integrations, then choose Github from the list on the left.
3. Click Install Github Integration. This sends you to the GitHub App install flow, where you choose the GitHub account (organization or user) and the repositories the app can access.
4. After installation, the settings page lists your connected accounts under Installed Github Organizations.

The Github tab on a work item

Open any work item to reveal its drawer, then switch to the Github tab (alongside tabs such as Assets and Activity). The tab shows:

• Linked Pull Requests — with counts such as N Open / N Closed.
• Linked Branches
• Linked Commits

Each linked PR carries its current status (Open, Draft, Closed, or Merged) along with review and check information.

Automatically linking pull requests

DevStride links a pull request to a work item whenever the item's number appears in any of the following:

• the PR's head branch name
• a commit message
• the PR title
• the PR description (body)

When a PR is opened, synchronized, or edited, DevStride scans these fields, matches any work-item numbers it finds, confirms the items exist in your organization, and links the PR to every matching item. Automatically linked PRs appear in the Linked Pull Requests list with no extra badge.

To make auto-linking easy, the bottom of the Github tab includes a helper panel:

Include <item-number> in your branch name, commit message, or pull request description to automatically link.

The panel also offers a copyable example branch name in the form <username>/<item-number>/<title>, so you can grab a ready-made branch name when you start work.

Manually attaching a pull request

If a pull request doesn't reference a work-item number in its branch, commits, title, or description, you can attach it by hand.

1. Open the work item and switch to the Github tab.
2. In the Linked Pull Requests section, click Attach a Pull Request (the link icon).
3. In the Attach Pull Request dialog, paste the full PR URL into the Pull Request URL field. The URL must be in the form https://github.com/<owner>/<repo>/pull/<number>.
4. Click Attach, or press the keyboard shortcut shown on the button. To back out, click Cancel.

On success you'll see a Pull request attached. confirmation, and the PR appears in the Linked Pull Requests list alongside any auto-linked PRs, with the same status, review, and check details.

The Manual badge and unlinking

A pull request you attach by hand displays a blue Manual badge in the Linked Pull Requests list and exposes an Unlink button on its row.

To remove a manually attached PR:

1. Click Unlink on the PR's row.
2. In the Unlink Pull Request confirmation dialog, confirm that you want to detach the PR from the item.
3. On success you'll see a Pull request unlinked. confirmation.

If you paste the URL of a PR that was already auto-linked, attaching it is idempotent: DevStride marks the existing link as manual rather than creating a duplicate.

Permissions

The Attach a Pull Request and Unlink controls require edit permission on the work item. Viewers without edit rights don't see these controls, and the server independently enforces the same permission — an unauthorized attempt is rejected with a "You are not authorized to link a pull request to this work item" error. Linking also requires an active organization subscription.

What this integration does not do

• There is no bulk or multi-PR attach — you attach one PR at a time by URL.
• There is no search-and-pick PR list — manual attaching is by pasting a URL only.
• You can't edit a PR from inside DevStride — the footer links (Conversation, Commits, Checks, Files Changed) open the PR on GitHub in a new tab.

Troubleshooting

If a manual attach fails, the message tells you what to fix:

• "A pull request URL is required." — the URL field was empty.
• "That does not look like a GitHub pull request URL." — the URL doesn't match https://github.com/<owner>/<repo>/pull/<number>. A trailing /, ?, or # is fine; anything else is rejected.
• No GitHub installation found for the owner — install the DevStride GitHub App on that account first.
• The DevStride GitHub App is no longer installed — reinstall it on that account and try again.
• The pull request could not be accessed — a 404 from GitHub. Check that the URL is correct and that the DevStride GitHub App has access to the repository.

Related

• Jira Integration
• Connect AI & the MCP Server
• Database Access for BI Tools