Skip to main content
PR triage skips automatic reviews of pull requests you do not want tested. New projects, new GitHub integrations, and new Azure DevOps repositories start with it on. Mappings created before that default stay off until you turn them on. Use Settings → Integrations → GitHub App or Settings → Integrations → Azure DevOps, the PR Triage toggle, and PR triage prompt. See Azure DevOps pull request testing. On GitHub, when QA.tech skips a pull request that has no earlier review result, the QA.tech / PR Review check is set to skipped with the reason, and QA.tech does not post a review comment. On Azure DevOps, a skip does not set a status. Comment @qa.tech on the pull request to run a review anyway. The prompt is a list of skip rules. Write them from the details in What the prompt can use. A rule about files skips the review only when every changed file matches it. A pull request that mixes a skippable file with a product change is still tested, unless a rule about the base branch, head branch, who opened it, or its deployments skips the whole pull request. If the prompt says to test the pull request, QA.tech runs the review. Docs-only, CI-only, and other untestable changes can still be skipped by the built-in rules even when your prompt does not mention them.

What the prompt can use

The prompt sees only the details in this table. It does not see the diff, your regression tests, or applications. A pull request that changes more than 40 files is reviewed. The prompt is not applied to that review.

Skip one scenario

Triage skips the whole review. To keep the review and leave out one scenario, add a PR Review Rule or an Agent Rule. For example, tell the agent not to run the billing scenario.

Updates to a pull request

The first review of a pull request is triaged against every file in that pull request. After a review finishes, a later push is triaged against only the diff since that review. A follow-up that only changes docs, CI, or other files your prompt skips can be skipped even when earlier commits in the same pull request changed the product. On GitHub, the QA.tech / PR Review check on the new commit keeps the previous review’s result, passed or failed, and a pull request that has not had a result yet still gets a skipped check with the reason. Azure DevOps does not set a status. The existing review comment stays as it is. If those new commits should be tested, QA.tech reviews the whole pull request again, not only the new commits. The finished review replaces the review comment. Comment @qa.tech to review the whole pull request anyway, including after a skipped update. If the reviewed commit is no longer in the repository, for example after a force-push that removed it, triage uses the full pull request diff.

Reviews started from the API or GitHub Action

A review started with POST /v1/chat/change-review or the change-review GitHub Action follows the PR Triage toggle by default, the same as an automatic review. To change this for one review, send triage options in the change-review request:
  • enabled: true lets triage skip the review even when the toggle is off.
  • enabled: false always runs the review.
  • prompt replaces the PR triage prompt for this review, up to 4000 characters. It does not turn triage on. Omit it or leave it empty to use the integration prompt.
A skip holds for that commit. With the prepare and review jobs, triage runs once on the prepare job, and the review job does nothing for a skipped commit. A later request for the same commit runs the review only when it sends enabled: false or someone has asked for a review with @qa.tech. A new commit is triaged again when prepare sends that commit’s commitHash (for example github.event.pull_request.head.sha), not the previous head still stored on the pull request row.

Suggested workflows

Use these as inspiration. Copy, combine, or adapt them. Skip untestable changes (default):
Skip one product area:
Only test flows a customer can see:
Skip dependency bumps:
Skip only docs and CI:
Skip pull requests from one account:
Skip a deployment environment:
Skip pull requests into one branch:
Skip a folder: