Repository workspaces
A repository's findings and history at any branch, pull request or commit, its review coverage, and its states.
Each repository you add has a workspace at /repos/<owner>/<repo>, showing its findings and commit history at one position (a branch, pull request or commit) and how well runs have reviewed it. To add a repository, see Add a repository to V12.
Open a repository
- From the sidebar. Pick a repository in the switcher. Findings, Runs and Autopilot then show only that repository, and Steers lists every Steer with that repository's rules, findings and runs.
- 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.
Findings and history
The workspace has two tabs:
- Findings: the findings at the position you picked. For views and filters, see Findings inbox.
- History: the commits of the branch or pull request, newest first, each with how many runs reviewed it and its findings. Click a commit to move the whole workspace to it.
When V12 can run the repository, New run in the header opens New run on it, at the position on screen; see Start a run.
Positions
The header has two pickers:
- Branch or pull request: the Default branch, other Branches, and the Open pull requests V12 knows about, shown as Pull request #n.
- Commit: the commits on that branch or pull request. Until you pick one, it shows the newest, marked latest.
To open a GitHub link in V12, replace https://github.com/ with https://v12.sh/ (organization address). Pull request links on any tab, commit links with a full or short SHA, and …/tree/<branch> links open the findings there. …/pull/42/commits opens the pull request's history. A file link (…/blob/<branch>/<path>) shows "V12 does not show files", with a link to that branch's findings.
If V12 can't place a position, such as a branch or pull request it has no record of, it says "Repository position unavailable" with the reason, and offers Open default branch followed by the branch name when it can.
Review coverage
Next to the tabs, the workspace shows how well runs cover the commit on screen. Only imported runs 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, and missed that many commits.
- Partially reviewed: a run's review of this commit 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.
Archived and disconnected repositories
A banner above the tabs flags a limited repository:
- "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:
- "owner/name isn't in organization.": for a GitHub repository, click Add owner/name. If you can't, V12 says why. Otherwise, use Open repositories, which opens Settings → Repositories, or switch organization.
- "V12 is preparing this repository. This page will update automatically." after you add a repository.
- "V12 hasn't reviewed name yet.": a public repository you added has no history in V12 until a run on it finishes. New run starts one.
When V12 can't add a repository
| Message | Fix |
|---|---|
| "GitHub is limiting V12's requests" | Click Try again in a few minutes. |
| "GitHub isn't connected" | An Admin clicks Install V12 on GitHub. |
| "owner/name is private" with "An owner of organization adds private repositories." | Only an Admin can add a private repository. |
| "owner/name is private" | V12's GitHub App doesn't have access. An Admin clicks Give V12 access to open the installation's settings on GitHub. |
| "V12 can't find owner/name" | Check the name. For a private repository, an Admin clicks Give V12 access. |
V12 says a repository is private only when your own connected GitHub account can see that it is. Otherwise it says it can't find it.
You may also see:
- Set up a workspace for owner: the repository belongs to a GitHub account other than this organization's. It starts setting up a workspace connected to that account.
- Install V12 on owner (Admins only): this organization isn't connected to a GitHub account V12 can use.
- Connect GitHub account: connect your own GitHub account first, in the GitHub section of Settings → Repositories.
GitHub and Settings open in a new tab. Back in V12, your search is kept: add the repository 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; it won't add it twice.