Skip to main content
The Repositories page shows every repository in the current GitHub App installation. Use it to enable or pause reviews without changing the GitHub App’s scope.

​
Two-layer model

Repository access in MergeWatch works in two layers:
1

GitHub App scope

Which repositories the GitHub App can access. Managed on GitHub under Settings > Applications > MergeWatch > Configure. This controls whether MergeWatch receives webhook events for a repo.
2

MergeWatch enabled/disabled

Whether MergeWatch actively reviews PRs in a repo. Managed on this page. A repo can be in scope on GitHub but paused in MergeWatch — webhooks arrive but are silently ignored.
Use the MergeWatch toggle to pause reviews temporarily without removing the repo from the GitHub App. This is useful during large migrations, hackathons, or periods of high churn where AI review noise is not helpful.

​
Summary strip

Above the card grid, a summary strip shows: X connected / Y active / Z paused These counts update in real time as you toggle repositories.

​
Card states

Each repository is displayed as a card with one of three states:

​
Toggling a repo

Click the toggle on any repository card to switch between Active and Paused. The change updates the enabled state in DynamoDB immediately. The UI uses optimistic updates with automatic rollback if the API call fails.
Only GitHub org owners can toggle repositories. Non-admin users see the toggles in a disabled state.

​
Configure on GitHub

The Configure on GitHub button opens the GitHub App installation settings page where you can add or remove repositories from the App’s scope. This controls the first layer — which repos MergeWatch can access at all.
Only GitHub org admins can modify the App’s repository scope on GitHub. This is a GitHub-level permission, not a MergeWatch restriction.

​
.mergewatch.yml badge

Repository cards display a badge when a .mergewatch.yml configuration file is detected at the root of the repo’s default branch. The file is detected on the first pull request webhook after installation. Click the badge to navigate to the .mergewatch.yml reference documentation.
If you add a .mergewatch.yml file to a repo that already has reviews, the badge appears after the next PR is opened. MergeWatch does not scan repos proactively — detection happens during webhook processing.