To keep your reports clean and relevant, you can archive benchmarks that were removed from your codebase. When benchmarks are permanently removed from your codebase, they will first appear as “skipped” in reports due to the partial runs feature. You can then archive these benchmarks to remove them from future reports.
Archived benchmarks can be restored at any time if needed.

Effects of archiving a benchmark

An archived benchmark will be completely removed from active reports. Archived benchmarks can be found in the Archived tab on the benchmarks page, and their individual dashboard pages remain accessible with full historical data. They can be restored from there. Archiving a benchmark on a pull request (where the benchmark was skipped) will remove the benchmark from the report.

How to archive a benchmark

Archiving PermissionsWhen working with an organization’s repository, only the admins are allowed to archive or restore benchmarks.

From the skipped benchmarks section

The most common way to archive benchmarks is to do it when they are removed from your codebase in a pull request.
  1. Navigate to the branch page where the benchmarks were skipped
  2. In the Skipped benchmarks section, click the archive button next to benchmarks that are no longer needed
  3. Confirm the archival action in the modal

From a benchmark’s dashboard

You can also archive individual benchmarks from their dashboard:
  1. Navigate to the benchmark’s dashboard by clicking on its name in any report
  2. Click the Archive button on the benchmark’s dashboard
  3. Confirm the archival action

How to restore an archived benchmark

You can restore an archived benchmark at any time:
  1. Navigate to the archived benchmark’s dashboard (found in the Archived tab on the benchmarks page)
  2. Click the Restore button
  3. The benchmark will reappear in active reports