Integration
Connect GitHub to your delivery record
Install the Stride GitHub App and pull requests stop being a separate universe. A PR that references a story shows up onthat story — with its merge state — so “is this actually done?” has an answer that nobody has to assemble by hand.
What connecting actually gives you
- Pull requests linked to stories — reference a story URL in the PR title or body and the link is made automatically.
- Merge status on the story — open, merged, or closed, without leaving the backlog.
- Draft PRs from a story — the one deliberate write back to GitHub, available to you and to connected AI agents over MCP.
- A repository allowlist — the App only sees the repos you pick, and you can change that later without reinstalling.
How the linking works
There is no commit-message syntax to memorise and no bot to mention. Put the story link anywhere in the PR title or body. All of these are recognised:
https://stride.page/stories/<storyId>
https://stride.page/projects/<projectId>/stories/<storyId>
[story](https://stride.page/stories/<storyId>) ← markdown links
…with a trailing slash, ?query, #fragment, or Mixed.Case hostLinks to any other host are ignored, so quoting someone else’s tracker in a PR description will not create a phantom link.
Direction, stated plainly
This is an inbound integration. GitHub tells Stride what happened; Stride does not manage your branches, reviews, or merges. The only write is a draft pull request you explicitly ask for. If you need Stride to be the system of record for work that currently lives in another tracker, that is the Jira Cloud migration, not this.
Security
- A GitHub App with a scoped repository allowlist — not a personal access token.
- Every inbound webhook payload is signature-verified before processing.
- Removing the member who connected the integration disables it, so access does not outlive the person who granted it.
Frequently asked questions
How do I connect GitHub to Stride?
Open Settings → Integrations → GitHub and install the Stride GitHub App. You choose which repositories it can see during install, and you can change that allowlist later without reinstalling. Stride never asks for a personal access token.
How does a pull request get linked to a story?
Paste the story URL into the PR title or body. Stride’s parser accepts the plain link, a markdown link, links inside code fences or blockquotes, and links with query strings, fragments, trailing slashes, or mixed-case hostnames. Links pointing at any other host are ignored.
Is this a two-way sync?
Mostly one-way: GitHub events flow into Stride. The single write in the other direction is opening a draft pull request from a story, which you or an AI agent trigger deliberately. Stride does not modify your branches, reviews, or merge state.
Which GitHub events does Stride consume?
Installation events (so the allowlist stays current), pull request events (open, update, close, merge), and push events. Payloads are signature-verified before they are processed.
Can an AI agent open a pull request?
Yes. Opening a GitHub draft PR from a story is exposed as an MCP tool, so Claude Code, Codex, or Cursor can raise a draft against the story they are working on. It is RBAC-gated like every other tool call and lands in the audit log.