Choosing which repositories get reviewed

Pick which Azure DevOps repositories ADO Pilot monitors using the onboarding wizard, and learn how repository enablement fits into the settings hierarchy.

Last updated

You decide which repositories ADO Pilot reviews. Today you make that choice in the onboarding wizard — pick the repositories during install, and ADO Pilot monitors only those. You can revisit the wizard any time to enable or disable repositories.

The wizard path (use this today)

The onboarding wizard runs the first time you sign in after installing ADO Pilot from the Azure DevOps Marketplace. You can re-enter it to change repository selection at any time.

  1. Open the customer dashboard at https://onboarding.adopilot.dev.
  2. Sign in with the Microsoft account that owns the Azure DevOps organization.
  3. From the dashboard, start (or resume) the onboarding wizard.
  4. Step through to the Select repositories step.
  5. Check the repositories you want ADO Pilot to monitor.
  6. Click Next and complete the remaining wizard steps.

When you save the wizard, ADO Pilot writes a repository-level enabled: true flag for each selected repository, and enabled: false for the rest. Service hooks for unselected repositories are ignored at the webhook gateway.

How enablement interacts with the hierarchy

Repository enablement is a scalar field — the most-specific scope wins. See Org, project, and repo settings hierarchy for the full merge rules.

  • If you set enabled: true at the organization level, every repository is monitored by default. You can still opt individual repositories out at the repository level.
  • If you set enabled: false at a specific repository, that repository is skipped even if the organization default is true.
  • If you set enabled: false at the organization level, ADO Pilot reviews nothing — even repositories that have enabled: true set, because the wizard writes the repository value but the organization opt-out short-circuits review evaluation.

A repository that is disabled never costs review credits (RC), no matter how many PRs are opened against it.

Adding a new repository later

When your team creates a new repository in Azure DevOps:

  • If your organization-level enabled is true, the new repository is monitored automatically using the inherited defaults.
  • If you only enabled specific repositories during the wizard, the new repository is not monitored until you re-run the wizard and add it.

Disabling a repository

To stop reviewing a repository:

  1. Re-enter the onboarding wizard from the dashboard.
  2. On the Select repositories step, uncheck the repository.
  3. Save and exit.

Open PRs that were already in flight finish their current review. New PRs and pushes are ignored.