Code Context
Connect a GitHub repo to a project and Runhuman learns your codebase. After that, every test you run on that project comes back with richer, more detailed results — bug reports that are grounded in your actual code instead of described in the abstract.
What you get
Tests still run the same way. The difference is in what comes back: extracted issues are more detailed, more specific, and easier to act on, because Runhuman knows what your codebase looks like.
If you connect a repo and run no other changes, the next test you run on that project will already benefit.
Setup
Code Context uses the same GitHub App that powers PR analysis and auto-issue-filing — no extra installation, no extra scopes.
- Open your project in the Dashboard and go to Project Settings → Repos.
- Click Connect a repo and pick one. (See the GitHub Integration section if you haven’t installed the App yet.)
- Runhuman starts learning your codebase in the background. You’ll see a status indicator on the repo row that flips to ready when it’s done.
That’s it. Once it’s ready, every new test on this project benefits.
Keeping it current (Sync)
Your codebase moves; Runhuman’s understanding of it has to keep up. Click Sync on the repo row anytime to bring it in line with your latest commits on the default branch.
You don’t need to Sync before every test — only when you’ve shipped meaningful changes you want reflected in upcoming results.
CI / PR workflows
For PR-triggered tests, the GitHub Action exposes two SHA inputs so the test reflects the code at the head of your PR rather than the default branch:
| Input | Purpose |
|---|---|
enable-code-context | Turn on Code Context for this run |
commit-sha | The commit your deployed app corresponds to (typically github.event.pull_request.head.sha) |
commit-base-sha | The base commit the PR is merging into (typically github.event.pull_request.base.sha) |
wait-for-code-context | Wait up to 90 seconds for the PR’s code to be ready before scoring |
When you set commit-sha and commit-base-sha together, results are tied to the code in your PR — useful when the issue you’re testing only exists on the branch.
See GitHub Actions → Code Context inputs for the full configuration table and a recommended PR workflow snippet.
Managing it
Everything lives under Project Settings → Repos:
- Disconnect a repo — stops Code Context for this project. The GitHub App installation itself stays in place.
- Sync — runs in the background, safe to trigger anytime.
Related
- GitHub Integration — installing the GitHub App and connecting repos
- GitHub Actions — using Code Context in PR workflows
- Agent Skills — agents using Runhuman get richer results automatically once Code Context is set up