Repository workspaces

Every repository you add to V12 has its own workspace at /repos/<owner>/<repo>. It shows the repository's findings and commit history at one position (a branch, a pull request or a commit), and how well runs have reviewed that position.

Open a repository

• From the sidebar. Pick a repository in the switcher. Findings, Runs and Autopilot then show that repository only, and Steers lists every Steer with that repository's rules, findings and runs. Pick All repositories to go back to the whole organization.
• From Settings → Repositories. Choose Manage repositories at the bottom of the switcher, then click a repository's name. A name opens the repository once it reads Ready, or Waiting for push for a repository V12 hosts.

To add a repository, see Add a repository to V12. If V12 refuses, see When V12 can't add a repository.

Findings and history

A repository workspace has two tabs:

• Findings lists the findings at the position you picked. Its views and filters are described in Findings inbox.
• History lists the commits of the branch or pull request, newest first and grouped by day. A commit shows how many runs reviewed it and the findings at that commit. Show more loads older commits. Click a commit to move the whole workspace to it.

When V12 can run the repository, the header has Run…, which sets up a run at the position on screen; see Start a run. For a GitHub repository, the header's … menu has Open on GitHub.

Positions

The header has two pickers:

1. Branch or pull request. It lists the Default branch, the other Branches and the Open pull requests V12 knows about. A pull request shows as Pull request #n.
2. Commit. It lists the commits on that branch or pull request. Until you pick one, it shows the newest commit, marked latest.

A commit opened on its own, outside any branch, shows No branch. When you look at an older commit of a branch or pull request, a line above the tabs says how many newer commits there are; Latest takes you to the newest.

To open a GitHub link in V12, replace https://github.com/ with https://v12.sh/<organization>/repos/, where <organization> is your organization's address. https://v12.sh/repos/ works too: it opens the repository in an organization of yours that has it.

A short SHA that matches several commits opens a list of them to choose from.

If V12 cannot place a position, for example a branch or pull request it has no record of, the page says "Repository position unavailable" and gives the reason. When it can, it offers Open default branch followed by the branch name.

Review coverage

Next to the tabs, the workspace shows how well runs cover the commit on screen. Only runs whose results V12 imported, and that did not fail, count:

• Never reviewed: no run has reviewed this commit, or an earlier one in the history V12 imported.
• Behind, with a number: the latest review is of an earlier commit. The number counts the commits it did not see.
• Partially reviewed: a run reviewed this commit, but its review did not complete.
• Reviewed: a run completed a review of this commit.

In the repository switcher, the mark beside each repository shows the same state, and the line at the bottom of the menu names it for the repository you point at; otherwise it counts the repositories reviewed and never reviewed.

Archived and disconnected repositories

A banner above the tabs says when a repository is limited:

• "This repository is archived. Everything here is read-only."
• "V12 no longer has access to this repository. Runs are disabled." Findings and history stay readable.

These messages replace the workspace entirely:

• "owner/name isn't in organization." You opened a link to a repository this organization hasn't added. For a GitHub repository, click Add owner/name to add it; the page then shows the repository. If you can't add it, the button is disabled with the reason under it, or V12 says why after you click it. Open repositories opens Settings → Repositories, which lists the repositories this organization has, or you can switch organization.
• "V12 is preparing this repository. This page will update automatically." V12 is still preparing a repository you just added.
• "V12 hasn't reviewed name yet." A public repository you added has no history in V12 yet: "V12 imports this repository's history when a run on it finishes." New run starts one.

When V12 can't add a repository

If V12 can't add a repository, it says why in place of the row or under the button, and keeps what you typed. Where the UI says "owner", it means an Admin.

V12 calls a repository private only when your own connected GitHub account can see that it is; otherwise it says it can't find it. Other buttons you may see:

• Set up a workspace for owner: the repository belongs to a GitHub account other than the one this organization is connected to. Review it from a workspace connected to that account; the button starts setting one up.
• Install V12 on owner: this organization isn't connected to a GitHub account V12 can use. For Admins only.
• Connect GitHub account: you have to connect your own GitHub account first. It opens the GitHub section of Settings → Repositories.

GitHub and Settings open in a new tab. When you come back, V12 reads the repositories again and keeps your search, but does not add the repository for you: add it again. If GitHub hasn't told V12 about the change yet, click Refresh access.

"Repository was added, but the repository list could not refresh." means the repository is in the workspace. Click Refresh repositories to read the list again; it doesn't add the repository twice.