Name the appliance check for what it proves #4

Merged

marcos-mendez merged 1 commit from ci/name-the-appliance-check into master

2026-09-29 00:19:53 -03:00

marcos-mendez commented

2026-09-28 01:05:50 -03:00

(Migrated from github.com)

Closes #3. Follows Keel-Linux/.github#12, which renames the reusable
job build-and-boot to boot-published-layer and makes a layer that has never
been published fail the job instead of passing it.

Comments and documentation only: nothing about this repository's behaviour
changes here. The rename takes effect the moment that pull request merges,
because this caller uses @main.

Branch protection on this repository's default branch requires the old check
name and must be changed to the new one when that merges. GitHub fails
closed, so the cost of forgetting is a locked repository and not an
unguarded one: a required context that is never reported leaves every pull
request blocked, waiting for a status that will never arrive. Measured on
keel-mariadb on 2026-09-28, two pull requests under the same rule with every
reported check green: number 16, reporting appliance / build-and-boot, was
clean; number 17, reporting appliance / boot-published-layer and identical
otherwise, was blocked. Renaming the rule is a maintainer step and is listed
in the body of Keel-Linux/.github#12 with the other repositories in the same
position.

Closes #3. Follows Keel-Linux/.github#12, which renames the reusable job `build-and-boot` to `boot-published-layer` and makes a layer that has never been published fail the job instead of passing it. Comments and documentation only: nothing about this repository's behaviour changes here. The rename takes effect the moment that pull request merges, because this caller uses `@main`. Branch protection on this repository's default branch requires the old check name and must be changed to the new one when that merges. GitHub **fails closed**, so the cost of forgetting is a locked repository and not an unguarded one: a required context that is never reported leaves every pull request blocked, waiting for a status that will never arrive. Measured on keel-mariadb on 2026-09-28, two pull requests under the same rule with every reported check green: number 16, reporting `appliance / build-and-boot`, was `clean`; number 17, reporting `appliance / boot-published-layer` and identical otherwise, was `blocked`. Renaming the rule is a maintainer step and is listed in the body of Keel-Linux/.github#12 with the other repositories in the same position.

Commenting is not possible because the repository is archived.

No reviewers