Repository navigation
Scratch: verify fork runner fallback for pingdotgg/t3code#11438 - #2
Project516 wants to merge 1 commit into
Conversation
Blacksmith runner labels only resolve for the pingdotgg org, so every job in CI, the mobile fingerprint check, and the Windows test lane queues forever on a fork. Pick the runner with case() on the repository owner so forks get the equivalent GitHub-hosted runner from the same workflow file.
There was a problem hiding this comment.
This PR adds fork runner fallback by replacing hardcoded Blacksmith runner labels with conditional expressions that select Blacksmith runners for the pingdotgg org and GitHub-hosted runners for forks. The change is applied consistently across ci.yml, mobile-fingerprint-check.yml, and windows-tests.yml. The logic is sound and the runner labels used for GitHub-hosted runners (ubuntu-24.04, macos-26, windows-2025) are valid.
review-bot, model nvidia/nemotron-3-ultra-550b-a55b:free, verdict approve
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: unavailable · PR result: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
|
Verification for pingdotgg#11438 is done. |
Temporary PR to run CI in this fork's context for pingdotgg#11438. Will be closed and its base branch deleted after the run.