Connect DevStride to GitHub so every work item shows the pull requests, branches, and commits that implement it — status, reviews, and checks included — without leaving DevStride.
Linking is driven by the item number. Put I1234 in a branch name, a commit message, or a pull request's title or description and DevStride links it to item I1234 automatically. A pull request that never mentions an item number can be attached by hand from the item's GitHub tab.
You need Manage Integrations in DevStride and permission to install GitHub Apps on the GitHub account or organization that owns your repositories. Linking also requires an active DevStride subscription.
Repeat for each GitHub account that owns repositories you want linked. Auto-linking runs from GitHub webhooks on the server, so nobody else needs to do anything.
Write the item number as a distinct token — I1234, [I1234], feature/I1234/show-repository, Fix I1234. A number buried inside a longer word or identifier is ignored. Workstream numbers (F42) are not linked.
| Where the number appears | What gets linked |
|---|---|
| Branch name (on push) | The branch shows under Linked Branches |
| Commit message (on push) | The commit shows under Linked Commits with its subject line |
| Pull request head branch, title, description, or any of its commits | The pull request shows under Linked Pull Requests |
DevStride re-scans a pull request whenever it is opened, edited, or synchronized, confirms each item exists in your organization, and links the PR to every matching item. One pull request can link to several items.
<username>/<item-number>/<title>. Copy it when you start work and the branch, its commits, and the eventual PR all link themselves.Open a work item and switch to the GitHub tab in its drawer. The tab appears only when your organization has the integration installed and the item is a work item, not a workstream.
2 Open / 1 Closed, the owner/repository of each PR, and its status: Open, Draft, Closed, or Merged. Expand a PR for its description, reviewers and review state, comment counts, and one line per check with its latest result.Use this for a pull request whose branch, commits, title, and description never mention the item number. You need edit permission on the work item.
https://github.com/<owner>/<repo>/pull/<number>. The repository's owner must have the DevStride GitHub App installed for your organization.You see Pull request attached. and the PR joins the list with a blue Manual badge and the same status, review, and check details as an auto-linked PR. If the attach fails, the dialog stays open with your URL so you can fix it — see Troubleshooting.
Attaching works for a merged pull request too, even one whose branch GitHub deleted on merge: the PR row still shows its original branch name and its checks, but the branch itself is not listed under Linked Branches. Pasting the URL of a PR that was already auto-linked does not create a duplicate; the existing link is marked Manual.
Only manually attached PRs show an Unlink button. Click it, confirm in the Unlink Pull Request dialog, and you see Pull request unlinked. Auto-linked PRs cannot be unlinked; they follow the references in the branch, commits, title, and description.
| Action | Requires |
|---|---|
| Install the app, see Installed Github Organizations | Manage Integrations |
| See the GitHub tab | Read access to the item |
| Attach a Pull Request, Unlink | Edit access to the item (enforced on the server too) |
| Any linking, automatic or manual | An active organization subscription |
| Message | What to do |
|---|---|
| A pull request URL is required. | The URL field was empty. |
| That does not look like a GitHub pull request URL. | Use 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 GitHub 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 (404) | Check the URL, and that the app has access to that repository. |
GitHub could not process a lookup for owner/repo#number (HTTP 422) | Check that the pull request and its latest commit still exist on GitHub. |
| GitHub returned a 5xx | GitHub itself is having trouble. Try again in a moment. Each GitHub request is given 20 seconds; a stalled GitHub fails inside a minute rather than hanging. |
| Needs updated permissions beside an installation | The DevStride GitHub App on that account is missing a permission the AI Assistant needs to read code (Contents and Pull requests, read-only). Click Review on GitHub and accept the requested permissions; the badge clears once GitHub reports them. |
| A branch or commit did not link | Check that the item number is a separate token (I123, not ABCI123) and that the repository is covered by the app installation. |
link_pull_request, unlink_pull_request, get_item_branches, and get_item_commits expose the same links to an AI assistantItem Request Forms
Build private or public forms that create work items (or Service Desk tickets) from a request, choose the fields and defaults, and share the link or offer the form inside DevStride.
Connect AI & the MCP Server
Where the Connect AI page lives, who can open it, what it gives you, and where the full MCP Server documentation is.