ci: register the Cloud VM image promote for dispatch

Merged
TE
25d ago
+47-0

Summary

.github/workflows/cloud-vm-image-promote.yml landed on feat-cmux-next in #25349, but it can't be dispatched yet: GitHub dispatches only workflows the default branch registers, so gh workflow run cloud-vm-image-promote.yml --ref feat-cmux-next returns 404.

This adds an inert registration on main with the same inputs. It follows the bake workflow's stub (#23681), which follows cmux-next-regenerate-bundles.yml (#18153). A dispatch runs the workflow file at --ref, so the feat-cmux-next implementation runs:

gh workflow run cloud-vm-image-promote.yml -R manaflow-ai/cmux --ref feat-cmux-next -f channel=dev -f snapshot=<sh-id> -f bake_run=<run id>

claude-sr2's decision on the workflow, word for word: "Same secret, same environment, contents: read, no new tokens: that's no new trust, and the dev channel is ours. Build the promote workflow exactly as you described, including the guarded delete_snapshot input."

Risk

  • None on main. The stub has permissions: {}, uses no environment and no secret, and only echoes.
  • The implementation's environment cmux-next-vm-image-dev allows only feat-cmux-next, so a dispatch from any other ref can't reach the key.

Testing

  • The file mirrors the feat-cmux-next inputs exactly (same names, types, defaults and choice options).
  • This PR's CI runs actionlint and the workflow guard tests.

No capture: CI workflow registration only

Changelog

none

Agent session: agent session

šŸ¤– Generated with Claude Code


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

Summary by CodeRabbit

  • Chores
    • Added a manually triggered workflow for cloud VM image requests, with a development channel option and optional snapshot settings.
    • When started, the workflow displays a message indicating that further processing is handled elsewhere.