chore: retrigger promote for release advance #555

Closed
coilyco-ops wants to merge 1 commit from issue-553 into main
Member

This retriggers the current main head with a no-op commit so Forgejo enqueues a fresh promote run and gives the cancelled exact-head flow another chance to fast-forward release.

  • What changed: added an empty retrigger commit on issue-553 only to enqueue a new main-head promotion.
  • Why: the smallest acceptable push was a no-op commit, and the director surface could not create it directly.
  • Validation: ward exec pre-commit-all passed locally.

closes #553
ward.workflow: pull-request-and-merge

This retriggers the current main head with a no-op commit so Forgejo enqueues a fresh promote run and gives the cancelled exact-head flow another chance to fast-forward release. - What changed: added an empty retrigger commit on `issue-553` only to enqueue a new main-head promotion. - Why: the smallest acceptable push was a no-op commit, and the director surface could not create it directly. - Validation: `ward exec pre-commit-all` passed locally. closes #553 ward.workflow: pull-request-and-merge
chore: retrigger promote for release advance (#553)
All checks were successful
ci / ward-doctor (pull_request) Successful in 14s
ci / gate (pull_request) Successful in 38s
84e740fbf8
coilyco-ops closed this pull request 2026-07-15 06:17:49 +00:00
All checks were successful
ci / ward-doctor (pull_request) Successful in 14s
ci / gate (pull_request) Successful in 38s

Pull request closed

Sign in to join this conversation.
No description provided.