PR Test Runs do not create a per-PR application sandbox or redeploy the services changed by the pull request. Your application target must already be deployed and reachable by the runner.
Set up PR Test Runs
1
Open PR Test Runs
In the web app, open PR Test Runs and select the repository you want to monitor.
2
Install the GitHub App
Install the Arga GitHub App on the selected repository. This lets Arga receive repository events and publish checks.
3
Choose a trigger
Select one of these modes:
- Pull requests runs when a pull request is opened, reopened, marked ready for review, or updated.
- Commits to branch runs on pushes to one selected branch.
4
Configure the run
Add optional repository-specific instructions. For pull-request triggers, choose whether Arga should also post a bot comment when the run finishes.
5
Save the settings
Enable validation. New matching GitHub events now create PR Test Runs and publish the result as an Arga Validation check.
Choose which tests run
Open Saved Tests, select a test associated with the repository, and choose one of these modes:- Automatically run relevant tests lets Arga select tests from the pull request or branch change.
- Run selected saved tests pins specific saved tests to the repository.
Review runs
The PR Test Runs page shows recent activity for the selected repository. You can search by branch name or pull-request number and see the status, commit SHA, trigger type, and start time. Open a row to inspect the run details. GitHub also links to the result from the Arga Validation check. If PR comments are enabled, Arga posts a completion summary on the pull request.Pause or skip validation
Use Disable validation to stop new automatic runs without removing the repository configuration. To skip one head commit, include[skip arga] in its commit message. Arga completes the GitHub check with a neutral result instead of starting a run.

