SETUP GUIDE

GitHub App Change Risk

Connect selected repositories to deterministic Change Risk checks without granting repository administration, Actions, secrets or organization-member access.

Before you start

  • Workspace owner access
  • Repository administrator access
  • The AntOps Change Risk GitHub App installed only on repositories you intend to connect

Setup

  1. Open Change Risk in AntOps and choose the GitHub App setup path.
  2. Complete the GitHub installation flow, then return to AntOps.
  3. Select only repositories shown by the verified installation.
  4. Open or update a pull request with supported static files and review the AntOps Change Risk Check Run.

Verify and expected result

AntOps verifies the installation server-side and accepts only repository IDs returned by that installation. A successful pull request receives one Change Risk Check Run.

Selected repositories are mapped to the current workspace. Pull-request analysis is deterministic and does not execute repository content.

Common safe checks

Repository is not listed

Update GitHub App repository access first, then restart setup. Do not try to supply a repository ID manually.

Check Run did not appear

Confirm the repository mapping and that a supported selected file changed in the pull request.

Security and revocation

AntOps maps a repository to one workspace only. It does not accept arbitrary repository selection, clone repositories or execute repository code.

Remove repository access from the GitHub App or uninstall the App. Remove any associated API key or GitHub Action secret separately if you also use that path.