Repository navigation
fix(ci): only deploy the API to production from main - #54
Merged
Merged
Conversation
deploy-api.yaml also triggered on feat/cloud-gate-** pushes, and none of its build, push or flyctl deploy steps checked the branch, so a push to such a branch (or a manual dispatch from any branch) deployed to the production Fly app. The comment claiming production still gated on main was wrong. Drop the temporary branch glob, gate the job on refs/heads/main, and remove the develop/pull_request conditions that can no longer fire. Refs: stackpanel-thq.2
cooper (czxtm)
had a problem deploying
to
docs-preview
September 23, 2026 12:22 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Contributor
|
Preview |
Contributor
|
Docs preview |
This branch had an error being deployed
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
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.
deploy-api.yamlalso triggered onfeat/cloud-gate-**pushes, and none of its build, push orflyctl deploysteps checked the branch. So a push to such a branch, or a manual dispatch from any branch, deployed to the production Fly app. The comment saying production still gated on main was wrong.This PR drops the temporary branch glob and gates the job on
refs/heads/main. It also removes the develop and pull_request conditions, which can no longer fire.Verification:
actionlintpasses.Refs stackpanel-thq.2