🔧 chore(ci): publish L6 + L5+L6 workflow files to main#115
Merged
Conversation
This was referenced Apr 26, 2026
ZaxShen
added a commit
that referenced
this pull request
Apr 27, 2026
ZaxShen
added a commit
that referenced
this pull request
May 20, 2026
ZaxShen
added a commit
that referenced
this pull request
May 20, 2026
🛠️ feat(scripts): glab-retry-merge.sh — retry-on-405 wrapper for glab mr merge (#115) See merge request trustmybot/plugin!28
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.
Summary
Cherry-picks two workflow YAML files only from
devtomain. The actual test infrastructure (Dockerfile, runner, fixtures, scorers, MCP server changes) lives ondevand is NOT in this PR.Why target main directly (not dev)
GitHub's
gh workflow runrequires the workflow YAML file to exist on the default branch (main) to be triggerable from any other branch. New workflows added on feature branches can't be triggered until the YAML lands on main. Standard GitHub gotcha.After this lands:
Per the lightest-to-heaviest doctrine.
Security audit (pr-reviewer ran 2026-04-26)
Verdict: APPROVE. Specifically verified:
No workflow injection: only
${{ ... }}expansions are repo secrets routed viaenv:, the trustedgithub.event.label.nameused in anif:comparison, andsteps.version.outputs.versionderived from in-repo.claude-plugin/plugin.jsonviajq.OAuth token security:
CLAUDE_CODE_OAUTH_TOKENdelivered to Docker via BuildKit--secretrather thanARG/ENV— won't end up in image layers (l5-l6-combined.yml lines 60-61).Trigger surface respects cost policy:
l5-l6-combined.yml: dispatch + tag only (no PR runs)l6-dogfood.yml: requires explicitL6label gating on PRsSoft-fail on missing secret:
l6-dogfood.ymlexits 0 cleanly when secret absent (line 41) → forks won't break redl5-l6-combined.ymlonly warns; Dockerfile ondevhandles the actual skipDiff scope: exactly the two YAML files, no stray changes.
Test plan
gh workflow run l6-dogfood.yml --ref dev(light L6)gh workflow run l5-l6-combined.yml --ref dev(heavy L5+L6)Why this PR exists at all
The system permission layer correctly defended against pushing to a feature branch targeting main without explicit doctrine cover. We have the cover now (pr-reviewer audit attached above), so the push went through.
🤖 Generated with Claude Code