Name the appliance check for what it proves #2

Open

marcos-mendez wants to merge 2 commits from ci/name-the-appliance-check into main

marcos-mendez commented

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

(Migrated from github.com)

Closes #1. 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 only: nothing about this repository's behaviour changes here. The
rename takes effect the moment that pull request merges, because this caller
uses @main.

This repository has no branch protection today, so nothing needs renaming in a
protection rule. When one is added, the check to name is
appliance / boot-published-layer, and it is worth reading what that check
proves first: it boots the layer the mirror publishes, which on a pull request
that changes the recipe is the code before the change.

Closes #1. 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 only: nothing about this repository's behaviour changes here. The rename takes effect the moment that pull request merges, because this caller uses `@main`. This repository has no branch protection today, so nothing needs renaming in a protection rule. When one is added, the check to name is `appliance / boot-published-layer`, and it is worth reading what that check proves first: it boots the layer the mirror publishes, which on a pull request that changes the recipe is the code before the change.

marcos-mendez commented

2026-09-29 00:18:57 -03:00

(Migrated from github.com)

The red check is not caused by this change: every run since 2026-09-26 stops at the missing tests/boot-test.sh (again on run 36516522252, same error), owned by #3. 7d94957 adds that to the header comment so it no longer describes a boot the check has never done here. No branch protection on this repository, so nothing is blocked.

The red check is not caused by this change: every run since 2026-09-26 stops at the missing `tests/boot-test.sh` (again on run 36516522252, same error), owned by #3. 7d94957 adds that to the header comment so it no longer describes a boot the check has never done here. No branch protection on this repository, so nothing is blocked.

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin ci/name-the-appliance-check:ci/name-the-appliance-check

git switch ci/name-the-appliance-check

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff ci/name-the-appliance-check

git switch ci/name-the-appliance-check

git rebase main

git switch main

git merge --ff-only ci/name-the-appliance-check

git switch ci/name-the-appliance-check

git rebase main

git switch main

git merge --no-ff ci/name-the-appliance-check

git switch main

git merge --squash ci/name-the-appliance-check