Skip to content

Deploy frontend after main CI#16

Merged
ridecontrol merged 1 commit into
mainfrom
infra/reliable-cloudflare-deploy
Jul 23, 2026
Merged

Deploy frontend after main CI#16
ridecontrol merged 1 commit into
mainfrom
infra/reliable-cloudflare-deploy

Conversation

@ridecontrol

Copy link
Copy Markdown
Collaborator

What changed

  • moves the production frontend deployment into the main CI workflow
  • makes deployment depend directly on the successful CI job for the same main push
  • keeps production build metadata linked to the merge commit and its pull request
  • removes the secondary workflow_run deployment workflow

Why

The prior deployment depended on a second GitHub workflow_run event. Previous merges deployed successfully, but the latest successful main CI run did not create that follow-up run, leaving Cloudflare on the older frontend build.

Impact

Pull requests continue to run CI without deploying. Every merge to main now runs CI and then deploys that exact SHA to the ridecontrol-frontend Worker using the existing protected Cloudflare token.

Validation

  • actionlint .github/workflows/ci.yml
  • bun run ci
  • 270 unit tests passed
  • TypeScript, Biome, Tailwind diagnostics, and production build passed

@ridecontrol
ridecontrol marked this pull request as ready for review July 23, 2026 07:21
@ridecontrol
ridecontrol merged commit ab02b16 into main Jul 23, 2026
@ridecontrol
ridecontrol deleted the infra/reliable-cloudflare-deploy branch July 23, 2026 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant