Skip to main content

Check each repository of a project

A project can hold several repositories, such as an app and its infrastructure. Compliance shows such a project as one row, but scans each repository on its own. Its page breaks the result down, so you can see which repository holds the gaps, and one that failed to scan does not hide the others. How a project gets more repositories is in Add or remove a project's repository.

Who can do this: anyone who can open Compliance. Running a new scan needs the permission to edit compliance.

  1. In the sidebar, select Compliance, then select the project's name in the list. Its page opens on the Overview tab.
  2. Find Repositories at the top, with the number of repositories, such as Repositories (2). A project with one repository has no such section: its page is that repository.
  3. Read each repository's section. The primary repository comes first, marked Primary. Each shows its own level, the Commit scanned and when it was Scanned, or Not scanned yet.
  4. Read the section's Gaps: its first five failing rules, each with its level. Select Show all to see the rest, and a rule's name to open the rule. Not scanned counts the rules whose check did not finish on that repository.
  5. To look at one repository only, pick it in Repository above the sections. All repositories shows them all again. The choice is kept in the page's address, so you can send the link to a teammate.
  6. If a section shows a red banner, that repository's scan failed, with the reason, such as Timed out after a time. The other sections keep their own results.
  7. Fix the cause, then select Rescan in the header to scan the project's repositories again. If a project keeps failing, Get every project a compliance level goes through each reason.

Under the sections, Gaps lists the failing rules with Fix and Fix all, as on any project; see Fix a repository's compliance gaps. Facts shows only the primary repository's facts, named after it.