Skip to content
Get started

GitHub integrationIn development

Proposed fixes, delivered as GitHub pull requests

The GitHub integration is in development. It is designed to let ROOKON read the code relevant to an issue and, when you authorize it, open a pull request with a proposed fix, so changes arrive in the review workflow your team already trusts.

Get started Try the live demos

The problem

Access to your code should be earned, scoped and visible

Any tool that touches source code has to be explicit about what it can read, what it can write and who decides. ROOKON's GitHub integration is being designed around least privilege and human approval from the start.

  • Personal tokens that can read every repository you own
  • Bots that push straight to protected branches
  • Changes nobody can trace back to a reason
  • Access that outlives the person who granted it

Live demo 1 of 3

Connect GitHub, see every permission

A simulated GitHub App installation: pick repositories, toggle pull-request proposals and see exactly what ROOKON can and can’t do.

  • Turn on “Propose fixes as pull requests”
  • Try “Push to main”

github.com · install ROOKON on acme

Simulated data

Repository access

LiveIntegration: In development
Only select repositories

Permissions GitHub will show you

MetadataReadList the repositories you selected (required by GitHub).
ContentsReadRead the code relevant to an issue.

ROOKON can

  • Read code in 1 selected repository

ROOKON cannot

  • Merge pull requests or deploy
  • Push to main or any protected branch
  • Change repository settings, secrets or workflows
  • Access repositories you didn’t select
  • Write anything at all (read-only mode)

Try it

How ROOKON helps

What you get

  • A GitHub App, not a personal token

    You install ROOKON's GitHub App on your organization and pick the repositories it may access. Access belongs to the installation, not to an employee's account.

  • Read-only until you opt in

    By default the app reads code and metadata to give analyses context. Creating branches and pull requests is a separate permission you enable explicitly.

  • Least-privilege permissions

    Metadata, contents and checks to read code and CI results, and pull requests to open proposals. Contents write only pushes ROOKON’s own branches. Optional: Actions read for failing test logs, and Workflows write only for a test setup you approve. No admin, secrets or member permissions.

  • Explicit approval per change

    Pull requests open only once an owner allows them. Rooky’s fixes start as drafts so your CI can test them, and become ready only when someone with approval rights accepts.

  • Your branch protection still applies

    ROOKON works on its own branches and never commits to your default branch. Required reviews and status checks apply exactly as for any contributor.

  • Audited and revocable

    Every repository read and every pull request is recorded in your audit log. Uninstall the app or remove a repository in GitHub and access ends immediately.

Live demo 2 of 3

Review proposed fixes in seconds

Every pull request ROOKON prepares lands in a review deck first. Swipe right to approve, left to ask for changes, up to look later. Simulated.

  • Approve with →
  • Request changes on the failing one

rookon · acme-cloud · commit requests

Simulated data
Livenew requests arrive while you review
6-day streak2 reviewed today0/6

#128rookon/fix-legacy-billing-interval → main

Fix upgrade failure for customers with a legacy “yearly” billing interval

low riskconfidence: high+20 −1 · 3 files
What happened
“Upgrade to Pro” throws for customers whose browser still stores the old “yearly” interval.
Expected benefit
Customers with the old setting can upgrade again; future missing prices are reported, not silent.
212 users affected+3 tests typecheck unit tests build

How a fix is designed to reach your repository

  1. 01

    Install the GitHub App

    Choose the organization and the repositories ROOKON may read.

  2. 02

    Read only what's relevant

    For each analysis, ROOKON fetches just the files connected to the issue.

  3. 03

    Write the fix and its tests

    Your AI provider proposes a fix with tests. ROOKON pushes it to its own branch as a draft pull request.

  4. 04

    CI runs the tests

    Your checks run before anyone reviews. If they fail, Rooky reads why and revises the fix.

  5. 05

    Review in ROOKON

    You see the diff, the tests and the results, and accept or decline. Accepting marks the pull request ready.

  6. 06

    Merge and deploy yourself

    Merging and deployment happen through your existing workflow.

Live demo 3 of 3

A proposed fix, as a pull request

A simulated pull request opened by ROOKON, with checks running. Review it like any teammate’s work.

github.com/acme/acme-cloud · pull/128

Simulated data

#128 opened

Fix upgrade failure for customers with a legacy “yearly” billing interval

rookon[bot] wants to merge into main from rookon/fix-legacy-billing-interval

  • typecheckrunning
  • unit testsrunning
  • buildrunning

Branch protection and required reviews stay in force. ROOKON only opens pull requests on repositories you authorized.

Try: Step through to your review

FAQ

Common questions

Is the GitHub integration available today?

Not yet. It is in development, and this page will be updated when it is available.

Which permissions will ROOKON request?

Metadata, contents, checks and commit statuses (read) for code context and CI results. If you allow pull requests, contents (write) to push ROOKON’s own branches and pull requests (write) to open them. Two optional extras for tested fixes: Actions (read) so Rooky can see why a test failed, and Workflows (write) only to add a test workflow when an owner approves a “Set up tests” change. Nothing beyond that.

Can ROOKON merge pull requests?

ROOKON never merges on its own. Every merge needs a person: either you merge in GitHub, or you tap Merge in ROOKON (Trusted-Rooky and Insane-Rooky only). With branch protection and required reviews in place, a pull request cannot be merged without approval from your team.

Does ROOKON keep a copy of my source code?

The design is to fetch files on demand for each analysis rather than mirror your repository. Snippets included in a proposal are stored with that proposal and follow your retention settings.

Will GitLab or Bitbucket be supported?

GitHub is the first source-control integration. Other providers will be considered based on customer demand.

Related

Be first to receive fixes as pull requests

Sign up now and connect GitHub as soon as the integration is available.

Get started with ROOKONExplore live demo