GitHub pull request reviews with the GitHub App

GitHub sign-in and repository access are separate

Signing in with GitHub identifies a teammate. It does not authorize repository reviews. A workspace manager connects a verified GitHub App installation separately and chooses which repositories to enable. One Code Voucher workspace can use a GitLab connection and one GitHub.com App installation together.

Before you connect GitHub

• Owner or administrator access to the Code Voucher workspace
• A GitHub.com personal account or organization whose App installation you can administer
• Access to the selected repositories through the deployment's configured GitHub App

Assign a developer seat in workspace settings to each teammate whose pull requests you want reviewed. Your trial includes capacity for 5 developer seats.

Code Voucher checks App permissions and repository access during setup. If a repository needs attention, follow the message in settings to finish connecting. Then choose the review feedback and checks you want your team to see in GitHub.

Connect a GitHub App installation

1. 1

   Open the workspace connection

   Open Settings in the intended workspace. In the GitHub connection card, choose Connect GitHub.
2. 2

   Authorize and select the installation

   Complete the GitHub authorization flow as an eligible installation manager. Choose a verified installation, or install the configured App when the connection flow offers that option. Select only the repositories this workspace should access.
3. 3

   Confirm the connection

   Return to Code Voucher and wait for ownership verification to complete. Confirm that the connection card shows the expected GitHub account or organization and a connected state.
4. 4

   Enable repositories explicitly

   Open Repositories, refresh discovery, and enable the intended GitHub repositories. A connected App does not automatically enable every repository.

Inspect your first pull request review

Confirm that the repository reports review intake as available, then open or update an eligible pull request. Draft pull requests are skipped by default. Code Voucher reviews the recorded source revision and keeps the review outcome, findings, and evidence in the private dashboard. Check the run against the pull request's current commit before acting on a finding.

See the security and code-quality review guide for what findings mean and how change review differs from a full audit. If no review starts, inspect repository availability and the recorded run reason before retrying; the troubleshooting guide explains review failures.

Choose summaries, inline findings, and checks deliberately

Dashboard review, provider feedback, and native checks are separate capabilities. A repository manager can choose the available summary or inline publication policy and native check mode. Raw reports and artifacts stay private; permitted provider feedback is classified before publication.

To require the review before merging, use the Gating check mode and configure the GitHub branch rule to require the exact code-voucher/review check from the expected App. Informational mode does not enforce the review threshold. Enabling checks in Code Voucher does not configure GitHub branch rules for you.

Current GitHub integration limits

• GitHub.com with one App installation per workspace; GitHub Enterprise and multiple GitHub organizations per workspace are outside the current boundary
• GitHub remediation pull request delivery is unavailable; a private patch proposal does not authorize provider publication
• GitHub Actions observation is optional and separately gated; workflow proposals require reviewed manual application
• No unrestricted workflow modification, generic CI retry, or merge-queue support
• Reconnecting an installation does not automatically re-enable previously disabled repositories

For the other provider workflow, read the GitLab integration guide. For credential and publication boundaries, read security and data handling.