Fix a repository's compliance gaps
A scan lists what fails on a repository as gaps. You don't fix them by hand: Fix files an ordinary task that changes the repository and opens a pull request. A gap turns green only when a later scan passes it, never when the pull request merges.
Who can do this: anyone with the permission to edit compliance and to create and edit tasks on the project. Without it, Fix is greyed out and the section says Fixing needs compliance edit and task create and edit access on this project.
File the fix
- In the sidebar, select Compliance. On the Repos tab, the Gaps column counts each project's failing rules, and Next gap names the one to fix first. Select the project's name to open its page.
- On the Overview tab, read Gaps (N). Each gap gives its rule, level and mode, how long it has failed, why it matters and what the scan found. With nothing failing, the section reads No gaps.
- Choose what to fix:
- Fix on a gap's row files a task for that rule alone.
- Fix all, at the top of the section, files one task that fixes every gap no fix is already working on.
- Check the banner above the tabs: Fix task created: and the task's number. Select the number to open the task and watch it run.
- Back on the project's page, each gap now carries the fix's state, which links to the task, or to the
pull request once it is open:
- Fix queued — the task waits for a free slot.
- Fix in progress — the task is running.
- PR open — the change waits for review and merge.
- Fix merged — rescan to confirm — the change is in, but no scan has checked it yet.
- Fix failed — the task could not fix it. Fix on the row tries again.
- Review and merge the pull request as you would any other.
- Once the fix is merged, select Rescan at the top of the page. While it runs the button reads Scanning…. A gap the fix closed leaves Gaps, and the project's level rises when enough of a level's rules pass.
A rule whose check did not finish on the last scan is listed under Not scanned instead, with its last result. It has nothing to fix yet: it offers Rescan in place of Fix.

If the task can't fix a gap, for example because it needs a decision only a person can make, answer its question on the task, or waive the gap for a time instead.
Related
- Fix a rule across many repositories — the same fix for many projects at once, lowest level first.
- Run a compliance scan — score your projects and rescan them every day.
- How compliance works — how a gap moves from a fix to green.
- Repository compliance — every section of a repository's page.