Repositories and branches

The repositories list shows every repository you connected. A repository's page lists its branches and where each one stands.

The repositories list

Repositories are grouped by the GitHub account they belong to. Click one to open its page. Edit takes you to GitHub to change which repositories verifAIed can see.

A repository's page

The default branch has its own card at the top. The other branches are grouped into three sections, most recently refreshed first:

  • Open PRs: branches on GitHub with an open pull request. The card shows the pull request number and its author.
  • No PR: branches on GitHub without one.
  • Local: branches whose coverage was uploaded from a machine rather than by CI.

Each card shows the commit it describes, when it was last refreshed, and how many functions are covered, partial and untested. When the card says changed functions, the counts are for the functions the branch changed compared with the default branch.

Use Filter branches… to search by name and the Author menu to show one person's pull requests. Sync reloads the list of branches from GitHub. Settings opens the repository's settings; see Repository settings.

A local branch is tracked separately from the branch of the same name on GitHub. That is what lets you verify work before it is committed or pushed. If the same branch also has CI coverage, it has two cards: one marked local and one not.

What each status means

StatusWhat it meansWhat to do
Up to dateThe latest coverage was read without problems.Nothing.
Needs attentionThe last refresh found a problem: no finished CI run had the coverage artifact, the artifact has expired, or the report is missing per-test data or junit.xml.Click the status to read the details, then fix your workflow.
FailedThe refresh could not be completed, for example because GitHub returned an error or the branch no longer exists.Click the status to read the details, then refresh again.
No CoverageCI has not run on this branch yet. verifAIed shows the functions the branch changed, without coverage.Push a commit and let CI finish.
Looking for a coverage artifact…The branch has never been refreshed and verifAIed is checking its CI runs.Wait a moment.
Not yet refreshed.A local branch that has no coverage yet.Upload coverage for it.

Inside a branch, the same problems are shown in full: No coverage artifact found and Refresh failed come with the message from the last refresh, and No CI coverage yet means you are looking at the changed functions only. CI coverage explains what the artifact has to contain, and Troubleshooting covers the common causes.

Refresh a branch

verifAIed refreshes a branch on its own when a CI run uploads coverage, and the page updates without a reload. To ask for it yourself, click Refresh on the branch's card. A local branch has no Refresh: it changes when you upload again.

Delete a local branch

Click Delete on a local branch's card. The branch moves to Recently deleted at the bottom of the page. From there:

  • Restore puts it back.
  • Permanently delete removes it together with the source that was uploaded for it. This cannot be undone.

Branches that come from GitHub cannot be deleted here.

Open a branch

Click a branch's card. A branch has three tabs:

  • Browser tests, where a branch opens: its recorded tests and their videos. See What browser tests are.
  • Unit: what your unit tests cover, function by function. See Unit coverage.
  • Manual: the code reached while someone clicked through the app by hand. See Code reached.