Skip to content

Adding a repository

When you add a repository, Drape imports its history so your dashboards have something to show before your next pull request. This page covers what Drape imports, how long it takes, and what each status on the repository card means.

What Drape imports

What How far back
Branches All of them
Pull requests The last 30 days first, open and closed, then older ones in the background
CI runs (GitHub Actions workflow runs) The last 30 days

After the import, Drape keeps the repository up to date on its own. You don't need to add it again or start another import.

Test results, coverage, and security scans are not imported from GitHub. They arrive when your CI uploads them with the Drape GitHub Action or the CLI.

How long it takes

Most of the time goes to CI runs. A small repository finishes in a few minutes. A busy one, with thousands of runs in the last 30 days, can take an hour or more. GitHub limits how fast Drape can read its API, so very busy repositories import in chunks and pause when they reach the limit.

You don't need to keep the page open. The import runs in the background, and the dashboards fill in as it goes.

Repository card statuses

These statuses cover a repository's first import. The repositories page refreshes itself while one runs.

Status What it means
Waiting to start The next step is about to start.
Importing branches Drape is reading the repository's branches.
Importing pull requests Drape is reading the repository's pull requests, starting with the last 30 days.
Importing CI runs Drape is reading the last 30 days of workflow runs. A busy repository imports them in batches, and the card counts the runs imported so far across all of them.
Import paused A busy repository's CI runs import in batches. Between batches, or while GitHub's rate limit resets, the import pauses and then resumes on its own.
Waiting to build dashboards The CI runs are in, and building the dashboards starts shortly.
Building dashboards Drape is working out pass rates, flaky tests, and CI time from what it has imported so far.
Import failed A step stopped with an error. Select See what went wrong for the details. Drape tries again on its next scheduled sync.
No test results yet The import is done, but no test results have been uploaded. Set up uploads to see test health and coverage.

While a step is waiting, running, or paused, select Details on the card to see it, with its progress and log. A failed card links to the same page as See what went wrong.