Skip to main content
Connecting GitHub lets Glassray read your repository to generate your spec - and link the pull requests that fix a deviation back to it. It’s how Glassray learns your agents’ intent straight from the source.

​
Connect

Open Integrations

In the dashboard, go to Settings → Integrations and click Connect to GitHub.

Install the Glassray GitHub App

GitHub asks where to install the Glassray app. Pick your account or organization and the repositories Glassray should see, then confirm. You land back in Glassray, connected.

Pick a repository

Choose the repo and branch Glassray should read - during onboarding, or later from the Deviations page (New spec).

Glassray generates your spec

Glassray reads the code and generates the spec (about 3–5 minutes), then starts finding deviations.

​
What the connection powers

Spec generation

Glassray reads your repo to build the spec - the rubric it judges traces against.

Pull request links

When a pull request mentions a deviation, Glassray links it to that deviation and keeps its state up to date.

​
Linking pull requests to deviations

Every deviation has a short ID, like DEV-142. To tie a pull request to it, use the deviation’s branch name - or put glassray-dev-142 anywhere in the PR title or description.

Copy the branch name

On the deviation page, click Copy branch name next to the title. It looks like glassray-dev-142-client-quote-isnt-the-clients-words. The fix you paste into your coding agent already tells it to use this branch.

Open a pull request

Push the branch and open a PR as usual. Glassray sees it within seconds - through the GitHub App’s pull request events, which Glassray turns on for you - and adds it to the deviation’s Pull requests panel.

Glassray comments once

Glassray posts a single comment on the PR - “Linked to Glassray deviation DEV-142” with the deviation’s name and a link back to it - so reviewers can see what the change is for. On a public repository the comment leaves the name out, so a deviation’s details never show up in public.
Glassray matches the glassray-dev-<n> form only - a bare dev-142 or DEV-142 in a branch name is ignored, so environment branches like dev-2 and other teams’ ticket keys never link by accident. A mention links automatically only from the repository your project’s spec was generated from; a PR in another repository is ignored, so attach it by hand instead. If your spec was pasted in under a project name rather than an owner/repo, there’s no repository to check, so a PR in any repository the app can see links - as long as only your organization uses that GitHub App installation. One PR can mention several deviations, and a deviation can have any number of PRs.
Automatic linking and the comment need the Glassray GitHub App. If your GitHub card in Settings → Integrations shows Legacy, your project uses the older GitHub integration: PRs don’t link on their own and Glassray doesn’t comment. Attach PRs by hand (below) - Glassray still refreshes their state about once an hour - or click Upgrade to GitHub App.
Each linked PR shows its current state:
A linked PR is information only. Merging it does not mark the deviation Done or change its status - you decide when a deviation is resolved.

​
Attach or remove a PR by hand

If a PR doesn’t carry the ID, or lives in a different repository, attach it yourself:
  • Deviation page - click + in the Pull requests panel and paste a PR URL, owner/repo#123, or just the PR number.
  • Slack - in the deviation’s thread, say @Glassray PR 123 is the fix for this.
  • MCP or Ask Glassray - use link_pull_request (and unlink_pull_request to take one off). See MCP server.
To take a PR off, choose Remove from its row menu. A removed PR stays removed - later updates to it won’t link it again.
Prefer not to connect your repository? You can bring your own spec instead.