Skip to content

chore(ci): add manual trigger to the image publishing workflow #2790

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
myftija merged 1 commit into from
Dec 16, 2025
Merged

chore(ci): add manual trigger to the image publishing workflow #2790

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
name: 🚀 Publish Trigger.dev Docker

on:
repository_dispatch:
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Replace repository_dispatch with workflow_dispatch to support manual triggering.

When triggered via repository_dispatch, data is available through github.event.client_payload, not the inputs context. Since jobs at lines 64, 71, 78 reference inputs.image_tag, the workflow will fail when triggered via repository_dispatch because that context is unavailable.

Use workflow_dispatch instead, which provides a 'Run workflow' button on the Actions tab for manual triggering and supports the inputs context. Apply this diff:

 on:
-  repository_dispatch:
+  workflow_dispatch:
+    inputs:
+      image_tag:
+        description: The image tag to publish
+        required: true
+        type: string
   workflow_call:
     inputs:
       image_tag:

If API-triggered runs are specifically required, add repository_dispatch with conditional input handling:

on:
  workflow_dispatch:
    inputs:
      image_tag:
        description: The image tag to publish
        required: true
        type: string
  repository_dispatch:
    types: [publish]
  workflow_call:
    inputs:
      image_tag:
        description: The image tag to publish
        required: true
        type: string

Then reference the tag conditionally: with: image_tag: ${{ inputs.image_tag || github.event.client_payload.image_tag }}

Verify whether API triggering is actually required, as the PR description only mentions "retry failures manually."

🤖 Prompt for AI Agents 
.github/workflows/publish.yml around line 4: the workflow is using
repository_dispatch which does not populate the inputs context (inputs.image_tag
is referenced later), causing failures when manually triggered; change the
trigger to workflow_dispatch and define the image_tag input so the inputs
context is available, or if API triggers must be supported, add both
workflow_dispatch (with inputs) and repository_dispatch plus conditional usage
of either inputs.image_tag or github.event.client_payload.image_tag in the job
step (e.g., set with: image_tag: inputs.image_tag ||
github.event.client_payload.image_tag).

workflow_call:
inputs:
image_tag:
Expand Down