Install the GitHub App

Install the GitHub App to run mutation tests for new pull requests in selected repositories.

Before you begin

Sign in to GitHub with permission to install the app for your account or organization. Organization policies may require an owner to approve installation. To create a Radforge account, you must have administration access to every selected repository visible to your GitHub user.

If your GitHub account is already connected to a Radforge organization, you must already be an owner or administrator of that Radforge organization. Ask an existing administrator for access rather than creating another account.

Install the app

1. Open Create your Radforge account. If you received an onboarding invitation for an existing Radforge organization, use that invitation instead.
2. Choose the GitHub account or organization to connect.
3. Under Repository access, choose Only select repositories and select the repositories that Radforge should test. Choose All repositories only if your organization has approved access to every current and future repository.
4. Review the requested permissions, then install the app.
5. When GitHub redirects you to Radforge, authorize your GitHub identity to complete onboarding.

Radforge links the installation and selected repositories to your Radforge organization. Removing a repository from the selection prevents new Radforge runs for that repository.

New organizations get ten trial analyses in total, shared across ChatGPT, CLI, and GitHub. The allowance does not reset when you reinstall. Trial runs allow one active analysis and a 20-minute timeout.

When installation succeeds, onboarding shows the connected organization and repositories. A supported pull request in a selected repository starts a Radforge GitHub check.

One pull-request run cannot span Go, TypeScript/JavaScript, and Python profiles. Split mixed-language changes into separate pull requests.

Run your first analysis

You can use the GitHub App without installing the CLI or obtaining a CLI API token.

1. Open Radforge Setup and confirm that your repository is Enabled. The free-trial panel shows analyses used, analyses in progress, and the remaining lifetime allowance.
2. Choose Open pull requests for that repository. Open a pull request with a supported source change, reopen one, or push a new commit to an existing pull request. Installing the app does not replay existing pull requests automatically.
3. Open the pull request’s Checks view and find the Radforge check. A queued or running check means the analysis has not finished.
4. After the check completes, follow its findings link. Confirm that the analyzed commit matches your pull request before acting on the findings.

Use a Go module or workspace with Go tests, a TypeScript/JavaScript project with Vitest and a supported lockfile, or a Python project with pytest, pyproject.toml, and uv.lock. Read Installation and prerequisites for the supported layouts and versions.

A survivor means the selected tests passed after Radforge changed the code’s behavior. Add an assertion or test case for that behavior, then push a new commit to analyze the change again. A setup failure or unsupported result does not prove that your tests catch faults.

If an analysis is already active, wait for it to finish before starting another trial run. Used analyses and active reservations both count against the ten-analysis limit. Infrastructure failures release their reservation; completed analyses, mutation timeouts, and cancellations consume an analysis.

Review permissions

The production app requests these permissions:

• Checks: read and write, to publish and update Radforge checks.
• Contents: read, to read source files for hosted runs.
• Metadata: read, required by GitHub Apps.
• Pull requests: read, to read pull-request changes.

It subscribes to pull-request events. Radforge does not request repository contents write access, issue write access, or administration permission.

Fix installation problems

If setup does not complete:

1. Confirm that GitHub permits you to install the app and that you have administration access to the selected repositories.
2. Allow cookies during the redirect between GitHub and Radforge.
3. Confirm that the repository is still selected in the GitHub App settings.

If Chrome reports ERR_BLOCKED_BY_CLIENT on the return to Radforge, ask your browser or security administrator to resolve the callback block. Then start a fresh signup from Radforge. An old OAuth callback can expire; do not reuse or share it.

Do not send OAuth codes, installation callback URLs, or API tokens to support.