mirror of
https://github.com/vercel/workflow.git
synced 2026-09-14 19:59:43 +08:00
Peter Wielander
2a2ff2bca7
The backport workflow's PR comments told people to "paste this commit SHA into the `ref` input". `ref` is the input's YAML name and appears nowhere in the Run workflow dialog, which labels inputs by their description. The one visibly ref-named control there is "Use workflow from", which selects the branch the workflow file is read from and rejects a raw SHA. Name the field by its visible label instead, and say which control it is not. Also correct what a manual dispatch actually buys you. A forced run skips the AI *decision*; it does not skip AI *conflict resolution*, which runs unconditionally whenever the cherry-pick conflicts. So "once the underlying issue is fixed, re-run" was the wrong advice for the failure that prompted this: every run since 2026-08-21 18:31 died on `API key budget exceeded` from the AI Gateway, including a forced dispatch that resolved its SHA and cherry-picked correctly before hitting the same wall. The failure comment now lists an out-of-budget key among the causes and carries the manual cherry-pick recipe, which previously lived only in the conflict comment that an infra failure never reaches. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>