ci(deploy): add workflow_dispatch to production deploy#28
Closed
i11v wants to merge 1 commit into
Closed
Conversation
Production deploys triggered only on push to main. When a merge push fails to dispatch an Actions run (a GitHub-side event-delivery miss), there was no way to kick a prod deploy without another commit. Add a workflow_dispatch trigger so production can be deployed on demand from the Actions tab or API against main. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KsHsBJEMEU1qsN61erBkF4
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The
#26merge (d1c6460, squash-merged intomainat 16:08:56Z) did not trigger a production deploy. Investigation:origin/maindid advance tod1c6460— the push is real.Deploy (production)isstate: active, byte-identical to the version that deployed#24, and correctly configured forpush: [main].deploy.ymlrun exists ford1c6460— and neither does thepull_request: closedcleanup run. The newest run of any workflow predates the merge.Conclusion: the merge push simply never dispatched any Actions run — a GitHub-side event-delivery miss (or repository Actions being toggled off). The workflow config itself is correct.
The gap this closes
deploy.ymltriggered only onpush. With noworkflow_dispatch, a missed push-trigger left no way to deploy production short of landing another commit. This adds a manual trigger so production can be deployed on demand from the Actions tab or the API againstmain— both as the immediate recovery for the missed#26deploy and as a permanent safety valve.Changes
.github/workflows/deploy.yml: add aworkflow_dispatch:trigger alongside the existingpush: [main].Note
This does not, by itself, deploy the current
main. Once merged, run Deploy (production) manually againstmain(Actions tab → Run workflow, orworkflow_dispatchvia API) to shipd1c6460.🤖 Generated with Claude Code
Generated by Claude Code