Skip to main content
Code access lets QA Wolf’s AI read the code in the repositories that you choose on GitHub. You turn it on when you connect GitHub through the QA Wolf Code app. QA Wolf has two GitHub Apps. A workspace connects through one of them, never through both. With code access, QA Wolf’s AI uses your code changes to find new features, create flows, and maintain flows. It also helps tell when a failure is a bug. QA Wolf never writes code. The app has read access to repository contents.

Requirements

  • Code access turned on for your workspace. Ask your QA Wolf representative to turn it on. Until then, the GitHub settings have no Read your code option.
  • An organization admin in QA Wolf. Other members see the state and the note “Only an organization admin can change this.”
  • An owner of the GitHub organization that installs the app. For a personal account, the owner of that account.

Turn on code access for a new connection

1
Open Workspace settings → Integrations and select Connect on the GitHub card.
2
In the Connect GitHub dialog, keep Read your code selected, then select Continue to GitHub.
3
In GitHub, install the QA Wolf Code app and choose the repositories.
4
Authorize the app when GitHub asks. GitHub then returns you to QA Wolf.
If you clear Read your code, GitHub asks you to install the QA Wolf app, and code access stays off. You can change the repositories and code access later.

Turn on code access for a workspace on the QA Wolf app

1
Open Workspace settings → Integrations. Open the GitHub card’s menu and select Configure.
2
Under What QA Wolf does, find “Read your code (off)” and select Turn on.
3
In GitHub, install the QA Wolf Code app and choose the repositories.
4
Authorize the app when GitHub asks.
QA Wolf Code replaces the QA Wolf app. QA Wolf removes the installation of the QA Wolf app after it links the new one, unless another workspace still uses that installation.

Update required status checks

A required status check in GitHub can name the app that must post it. After the change, QA Wolf Code posts the checks, so a rule that names the QA Wolf app stops matching.
Until you update the rule, a pull request waits for a check that never comes.
1
In GitHub, open the branch protection rule or the ruleset of each protected branch.
2
Find each required status check that names the QA Wolf app as its source.
3
Change the source to QA Wolf Code, or to any source.
Do the opposite when you turn code access off.

Turn off code access

1
Open Workspace settings → Integrations. Open the GitHub card’s menu and select Configure.
2
Under What QA Wolf does, select Turn off.
3
In GitHub, install the QA Wolf app and choose the repositories.
4
Authorize the app when GitHub asks.
5
Change each required status check that names QA Wolf Code.
The QA Wolf app can’t read your repositories, only the changes in pull requests. QA Wolf’s AI then stops reading your code. Testing keeps working.

Permissions of QA Wolf Code

QA Wolf Code has every permission of the QA Wolf app, plus three: contents: read, actions: write, and members: read. GitHub shows these permissions when you install the app. The app subscribes to these events: deployment_status, issue_comment, issues, pull_request, pull_request_review_comment, push, status, and workflow_run. GitHub also sends installation and check_suite to the app without a subscription. QA Wolf uses installation to record a removed or suspended app, and check_suite to record the head commit of a check suite.

Approve the new permission

If your organization installed QA Wolf Code before it asked for the actions permission, GitHub asks an organization owner to approve it. Until an owner accepts, QA Wolf can’t use that permission, and the feature that needs it doesn’t work. In GitHub, an owner opens the organization’s installed GitHub Apps, opens QA Wolf Code, and accepts the new permissions.

States of code access

While GitHub has the app suspended, it sends QA Wolf no events, so the tests of deployments and pull requests also stop.
Last modified on November 19, 2026