You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: register a homelab-ci runner for the merge-danger scorer #212
PR kit v84 adds .github/workflows/merge-danger.yml. It runs on [self-hosted, Linux, homelab-ci]. This repo's online runners carry only m3d-linux-kvm and m3d-mac-vz, so the scorer job would stay queued and never post a merge-danger status.
Without that status, land-pr/danger.ts reports "waiting" for every PR, and after 60 minutes the merge takes the owner's word. Agent merges stop for the whole repo.
Fix, from agents-config kits/pr/ROLLOUT.md step 4a:
Register a homelab-ci runner for AojdevStudio/materialize-3d on the homelab-ci runner VM (Proxmox VM 120), like github-runner-ci-prosper-care.
Confirm /etc/merge-danger/typesafe_api_key is readable by github-runner there.
On VM 120, register a dedicated repository runner using the existing github-runner-ci-prosper-care setup as the reference, with Linux and homelab-ci labels. Keep registration credentials out of tracked files.
Verify the runner service is online and that its github-runner account can read /etc/merge-danger/typesafe_api_key without exposing the key. Confirm the repository Actions runner list includes an online runner with all required labels.
Once the kit workflow is available, run it on a PR and verify the job is picked up and posts the merge-danger status for that PR’s head. Keep the kit install PR blocked until this end-to-end check passes.
The current repository workflows target m3d-linux-kvm; .github/workflows/merge-danger.yml is not yet present on the checked-out default branch. No duplicate was found.
Activity
pullfrog commentedon Nov 8, 2026
Plan
github-runner-ci-prosper-caresetup as the reference, withLinuxandhomelab-cilabels. Keep registration credentials out of tracked files.github-runneraccount can read/etc/merge-danger/typesafe_api_keywithout exposing the key. Confirm the repository Actions runner list includes an online runner with all required labels.merge-dangerstatus for that PR’s head. Keep the kit install PR blocked until this end-to-end check passes.The current repository workflows target
m3d-linux-kvm;.github/workflows/merge-danger.ymlis not yet present on the checked-out default branch. No duplicate was found.gpt-6.1-terra| 𝕏AojdevStudio commentedon Nov 8, 2026
PR #213 installs kit v84 and waits on this issue before it merges.