GitHub integration

What it does

The GitHub integration mirrors the Linear one, but for teams that live in GitHub Issues. From any Ochre conversation, file a GitHub issue. Comments sync both ways. Status changes on the issue flow back to the conversation.

If your engineers use GitHub Issues directly (not Linear), this is your escalation path.

Setup

GitHub uses a GitHub App install, not user OAuth. This matters because:

• The install is scoped to specific repositories you choose, not your entire account.
• Access does not depend on a single user. If the installer leaves your company, the integration keeps working.
• Permissions are explicit and visible in your GitHub settings.

To set up:

1. Go to Settings → Integrations → GitHub.
2. Click Install GitHub App.
3. Choose your GitHub organization (or personal account).
4. Pick the repositories Ochre can file issues into (or "all repos").
5. Confirm. You're back in Ochre, connected.

You can change which repos Ochre has access to later by going to GitHub → Settings → Applications → Ochre → Configure.

Creating an issue from a ticket

In any conversation, click Create GitHub issue. The panel asks for:

• Title.
• Body. Defaults to a clean summary of the conversation, with a link back. Markdown supported.
• Repository. From the list of repos Ochre has access to.
• Labels (optional).
• Assignee (optional).

Click Create. The issue gets created in GitHub, the ticket links to it, and the issue number (owner/repo#42) shows on the conversation panel.

Two-way comment sync

Once linked:

• GitHub → Ochre. New comments on the issue appear as system updates on the ticket.
• Ochre → GitHub. Internal notes can be opted-in to post as GitHub comments. External replies to the customer never sync.

When the issue closes, the ticket gets a "GitHub: Closed" badge. You can configure auto-close on issue closed if you want.

Status sync

Issue state changes (open → closed, reopened) flow back into the conversation as system updates, so the agent sees engineering's progress without leaving the inbox.

Auto-link by issue reference

If a customer or agent mentions an issue reference in a message (#42 or owner/repo#42), we auto-link the ticket. Same as Linear.

Multiple installs

You can install the GitHub App in multiple organizations (e.g. your-company and your-company-internal). Repos from any installed org are available when filing issues.

Disconnecting

To disconnect, click Disconnect on the integration page or remove the GitHub App from GitHub directly. Existing links remain in the data but stop updating. Reinstalling the App restores sync for new activity.

See Disconnecting integrations.

Permissions

The GitHub App requests:

• Issues: Read & write. To create issues and post comments.
• Pull requests: Read. To detect linked PRs.
• Metadata: Read. Standard for any GitHub App.

We do not request access to code contents. We don't read your source. See Integration permissions.

The GitHub App access token is stored encrypted at rest. It's only readable through a server-side helper that checks the caller is an Owner or Admin of the workspace.

What's next

• See Linear integration for the Linear equivalent.
• Build Routing rules that auto-file high-severity bugs.
• Read Integration permissions for security details.