• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / cli / 40884283036
47%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 29 Oct 2026 01:42PM UTC
Jobs 1
Files 119
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

29 Oct 2026 01:41PM UTC coverage: 46.568%. Remained the same
40884283036

push

github

web-flow
ci(cli): add a report-only CLI benchmark for pull requests (#7363)

Adds a non-blocking job that compares the CLI build of each ready pull
request into `develop` with a build of the `develop` commit it branches
from, without Docker, a database, or the network. It writes a job
summary that leads with the answer ("no changes found" or "N things to
check"), then one plain-words line per flag (including when a command
that made no Management API calls starts making them), a before/after
timing table per command, API call counts, binary size, and a collapsed
section with timing ranges, per-command API calls, and the slowest
phases for commands that moved.

The first push to a pull request from this repository benchmarks and
posts one comment with the same report, tagged with a hidden marker.
Later pushes skip the benchmark while that comment reports a result, and
the job summary says so. Pull requests from forks have a read-only
token, so they get the job summary only and benchmark every push.

A maintainer can comment `/bench` to run the benchmark again on the pull
request's current head commit. The command re-runs that commit's
workflow run (the same as "Re-run all jobs" in the Actions UI), and the
re-run updates the comment in place. An eyes reaction on the `/bench`
comment means GitHub accepted the re-run; the result arrives as the
updated benchmark comment, whether it succeeded or failed. If nothing
can be re-run, the pull request gets a reply saying why: a benchmark is
already running, the run is older than 30 days, GitHub refused the
re-run, or there is no run for the commit. The comment keeps a collapsed
"Previous runs" list (commit, time, headline, link; up to 20) in a
hidden marker. Only the repository owner and people with write access
can run it, and only on open, non-draft pull requests into `develop`
from this repository. The whole comment must be exactly `/bench`; any
other comment is ignored. Comment-triggered workflows run from the
default... (continued)

5591 of 12006 relevant lines covered (46.57%)

25.09 hits per line

Jobs
ID Job ID Ran Files Coverage
1 40884283036.1 29 Oct 2026 01:42PM UTC 119
46.57
GitHub Action Run
Source Files on build 40884283036
  • Tree
  • List 119
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #40884283036
  • f8bcf892 on github
  • Prev Build on gh-readonly-queue/develop/pr-7369-96781a40268a5da929f22f5637b892966e9419e6 (#40873968264)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc