Skip to main content

Integration · GitHub

Open GitHub Issues Straight From Session Replay

Click "Open issue" in Relyv. We attach the session replay, console errors, repro steps, and tag the right reviewers based on CODEOWNERS.

Start free See pricing

What you get

CODEOWNERS-aware

We parse your CODEOWNERS and tag the right reviewers based on the page or component the bug touched. No more "who owns this file?" questions.

Replay-linked issues

Every issue body has the replay link, console errors, network HAR, and AI repro steps. The dev opens it with one click — no SSO juggling.

Branch-protection friendly

Issues created by Relyv use a bot account so your branch-protection rules and required-review counts work as expected.

GitHub Enterprise ready

GitHub.com and GitHub Enterprise Server (3.6+) are both supported. Self-hosted teams: we never proxy your issues through us.

Setup in four steps

  1. 1

    Install GitHub App

    Install the Relyv app from the GitHub Marketplace. Org admin approves; per-repo permissions are scoped at install time.

  2. 2

    Map repos to Relyv projects

    Choose which repos receive issues from which Relyv projects. Optional: parse CODEOWNERS to auto-assign reviewers.

  3. 3

    Trigger from a session

    In any session, click "Open issue" and pick GitHub. Title, body, labels, and assignees are pre-filled.

  4. 4

    Issue created with reviewers tagged

    The issue appears in your repo with the right CODEOWNERS auto-mentioned. Branch protection, required reviews, and project boards work normally.

Implementation details

CODEOWNERS parsing

When the user reports a bug from a specific page, we map the page to the repo path (configured per-project) and pick CODEOWNERS for that path. Multi-CODEOWNERS files are honoured; @-team mentions are preserved. If no CODEOWNERS match, the issue gets the default reviewer set you configure.

Bot account vs personal account

Relyv uses a bot account by default — issues are attributed to the bot, your branch protection rules treat them as machine-generated, and required-review counts include human approvals only. If you prefer personal-account attribution, individual users can connect their own GitHub identities.

GitHub Enterprise specifics

GHES 3.6+ is supported. Self-hosted teams can install the app via the standard GitHub Apps flow. Network: Relyv's server makes outbound HTTPS calls to your GHES instance — no inbound webhooks needed for issue creation, only for two-way sync (which is opt-in).

Frequently asked

Does this require GitHub Enterprise?

No. GitHub.com (Free, Pro, Team, Enterprise Cloud) and GitHub Enterprise Server (3.6+) are all supported.

What permissions does the GitHub App need?

Read metadata + CODEOWNERS, write issues, read issue state for two-way sync. No code-content access, no PR write, no admin scopes. Per-repo permissions are scoped at install time.

Can the same Relyv project file issues to multiple repos?

Yes. Default destination per project, plus rule-based routing — "checkout bugs go to monorepo, marketing bugs go to landing-site repo".

How does this interact with GitHub Issues forms / templates?

If your repo has issue forms (.github/ISSUE_TEMPLATE/*.yml), Relyv uses the form fields automatically — Title, Description, Labels, etc. Custom fields are mapped from Relyv metadata where the names match.

Related features

Other integrations

Ready to wire up GitHub?

Click "Open issue" in Relyv. We attach the session replay, console errors, repro steps, and tag the right reviewers based on CODEOWNERS.

Start free See pricing