Skip to main content
RepoFixer

Integrations · GitHub

Connect a repository or org

RepoFixer connects to a GitHub repository or organization to pull in the work you point it at, run a coding agent against it in an isolated environment, and open a small, human-reviewed pull request back into that repository.

Verified integration

  • Scope of access

    The connection uses OAuth with repo, read:org, and read:user scopes: enough to read repository content, open pull requests, and identify your account and org. It does not request admin or billing scopes. Build and deploy work uses a separate, narrower single-repository token rather than the broader connection credential.

  • How the PR gets opened

    A change is committed to a new branch prefixed repofixer/ and opened as a pull request against your default branch. Pull requests are capped at 100 changed files; a change that would exceed that isn't published as one oversized diff.

  • Review and merge model

    RepoFixer never merges. The PR shows up in your repository like any other. Your team reviews, requests changes, or merges it through your normal GitHub workflow.

  • GitHub + Jira together

    Connect Jira as well and a synced ticket can be the thing that starts a run, and the resulting PR still opens against the GitHub repository you've connected.

Setup

  1. 1

    Connect your GitHub account or organization from RepoFixer.

  2. 2

    Choose which repositories RepoFixer can work in.

  3. 3

    Send it a ticket, or create one directly, to start a run.

  4. 4

    Review the pull request it opens like any other PR.

GitHub integration FAQ

Got backlog work piling up? Tell us about your stack and we'll help you get a first run going.

support@repofixer.com