ci: activate NixOS testable-PR builder on the default branch (release)#495
Merged
Conversation
This was referenced Jun 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this is needed:
nixos-pr-build.yml(the trusted, label-gated testable-PR builder) was merged tomainin #493 — but it's apull_request_targetworkflow, and GitHub only fires those from the repository's default branch. brickbots' default isrelease, which doesn't have the workflow (or.github/scripts/), so labeling atestablePR currently does nothing.This adds exactly the three files from #493 to
release(the rotatedpifinder:Vkem…key included):.github/workflows/nixos-pr-build.yml.github/scripts/publish_manifest.sh.github/scripts/update_manifest.pyOnce merged, a
testable/previewlabel on a PR builds on the Pi5 → pushes the closure to thepifindercache → writes the PR's entry tonixos-manifest, all in the trusted base-repo context.Alternative to this PR: switch the repo's default branch to
main(where the builder already lives, CI-aligned) — that's an admin setting and would make this PR unnecessary.🤖 Generated with Claude Code