From b2182dd403b55e79771584b669dde3ce5f962962 Mon Sep 17 00:00:00 2001
From: Tobias Leinss <7684178+leinss@users.noreply.github.com>
Date: Thu, 27 Aug 2026 12:27:41 +0200
Subject: [PATCH] ci: allow the deploy workflow to be triggered manually

A run can be created with zero jobs attached to it. It then sits in
`queued` indefinitely and `gh run rerun` does not recover it, because
rerun replays the same run object rather than creating a new one. Only a
new run object clears the state.

Without `workflow_dispatch` the only way to produce one is a throwaway
commit on the deploy branch. The default branch is `release`, which is
where the workflow file lives, so the manual trigger is available.
---
 .github/workflows/deploy.yaml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/.github/workflows/deploy.yaml b/.github/workflows/deploy.yaml
index 0324f2500..8127942ef 100644
--- a/.github/workflows/deploy.yaml
+++ b/.github/workflows/deploy.yaml
@@ -7,6 +7,11 @@ on:
   pull_request:
     branches:
       - release
+  # Manual trigger. A run can be created with zero jobs attached, in which case
+  # it sits in `queued` forever and `gh run rerun` cannot recover it: rerun
+  # replays the same empty run object. Only a new run object recovers, and
+  # without this a throwaway commit is the only way to make one.
+  workflow_dispatch:
 
 permissions:
   contents: write