ci: guard Testbox workflows behind repository check (missed in #48)#49
Merged
Conversation
Same fork-guard as #48 for the four Testbox experiment workflows — their Blacksmith pools (incl. 32vcpu) queue forever on this fork; two of them sat 'pending' on #48 itself for 30+ minutes. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
…izmor template-injection) Canonical zizmor remediation — the expansion moves to env: and the PowerShell block reads $env:TARGET_REF. Surfaced because #49 touched the file, making security-fast's changed-files zizmor audit it for the first time; the finding predates the guards.
Author
|
Anvil review: fixed-ready.
|
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
1 participant
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.
Completes #48: the four Testbox experiment workflows were missed in the first sweep — two of them ("Blacksmith Testbox", "Blacksmith Build Artifacts Testbox") sat queued for 30+ minutes on #48 itself, demonstrating the disease. Same one-line guard per job; functional CI untouched.
Real behavior proof
Behavior or issue addressed: Four Testbox workflows queue forever on this fork (Blacksmith pools incl. 32vcpu not provisioned), leaving eternal pending checks on every PR.
Real environment tested: This repository's live Actions history — the two Testbox checks observed stuck-queued for 30+ minutes on PR #48 today (runs 26906163699 / 26906163598, status queued, no conclusion).
Exact steps or command run after this patch: ruby YAML parse of all 4 edited files; grep verification of exactly one job-level if per file.
Evidence after fix: Copied output:
Observed result after fix: On BenchAGI/openclaw these jobs evaluate if to false and report skipped; upstream behavior unchanged (condition preserved verbatim).
What was not tested: Upstream execution (this fork cannot exercise upstream CI; guard preserves their conditions verbatim).
🤖 Generated with Claude Code