ci: register cmux-next regenerate bundles for dispatch

Merged
TE
1mo ago
+27-0

Summary

Lanes can't run bun locally, but they still need to regenerate the committed agent-pane and settings-page bundles. The feat-cmux-next PR #18154 adds cmux-next-regenerate-bundles.yml, a dispatch that builds them for a lane branch.

GitHub dispatches only workflows the default branch has: dispatching the PR branch's copy returned HTTP 404: workflow cmux-next-regenerate-bundles.yml not found on the default branch. This adds an inert registration on main with the same inputs, as main already does for cmux-next.yml. Dispatches use --ref feat-cmux-next, so they run the feat-cmux-next implementation.

Testing

  • actionlint is clean.
  • python3 -m unittest tests.test_ci_fork_runner_routing tests.test_ci_workflow_guards_are_wired: OK.
  • python3 scripts/verify-local.py: passed.

Changelog

none

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.


Summary by cubic

Registers an inert cmux-next-regenerate-bundles.yml workflow on main so lanes can dispatch the real implementation on feat-cmux-next.

GitHub only dispatches workflows present on the default branch, so the previous attempt from the PR branch returned HTTP 404. This adds a registration-only workflow with the same inputs as the feat-cmux-next version; dispatches pass --ref feat-cmux-next, which runs the actual bundle regeneration.

Summary by CodeRabbit

  • Chores
    • Added a manually triggered workflow that accepts a target branch and optional commit SHA, then displays an informational message. It does not regenerate bundles.