supabase / cli / 37786830040
67%
develop: 67%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7122-7428f5ecc563ae354f86a347a49a0ee58a43feb1
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 79
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
coverage: 66.737%. Remained the same
37786830040

push

github

web-flow 
ci(release): gate hotfix pull requests into main (#7050)

Linear: [CLI-2442](https://linear.app/supabase/issue/CLI-2442)

Hotfix PR gating, the first of three PRs that complete the hotfix flow
on top of the branch and release work from #7038. A hotfix is a
`hotfix/*` PR into `main` with a `fix`, `perf`, or `revert` title;
squash-merging publishes the next stable patch and the existing sync
carries it back to `develop`.

- **Check Deploy** always runs and reports. On the scheduled `develop`
promotion it succeeds. On `hotfix/*` heads it requires the title to
start with `fix`, `perf`, or `revert`, with an optional scope and no
`!`, and the failure message says what to change. Any other head fails,
and so does a fork head on either path: hotfixes come from this
repository. The job is named so it can become a required status check on
`main` later; because `main` has no App bypass, the promotion's head SHA
must carry a real success for the deploy fast-forward push to pass.
- **Release Smoke Test** triggers on hotfix PRs into `main` and runs the
shared release pipeline with `dry_run: true`, restoring the
build-and-smoke rehearsal that beta normally provides. Dispatch inputs
keep their defaults. Runs are per-PR concurrent with cancel-in-progress,
and fork pull requests are skipped since their token cannot hold the
permissions the shared workflow declares.
- **Release dispatch guard**: a non-dry-run stable release can only be
dispatched from `main`. The `hotfix/*` exemption existed for the manual
rehearsal, which this PR makes automatic. @Coly010, was a real stable
publish from an unmerged hotfix branch intended? If so, say so and I
will restore it.

Verified on a scratch repository: with a ruleset requiring only this
check on `main`, a direct push of a deploy PR head and of a hotfix PR
head both passed once the job had reported on the head SHA, and a push
with no check run was rejected (rule suites 4418391424 and 4418634505).
The runbook's hotfix section and ... (continued)

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37786830040.1 79
66.74
GitHub Action Run
Source Files on build 37786830040