Repository navigation
Conversation
Adds a deploy job that runs after CI on pushes to master: applies remote D1 migrations, builds and deploys the Worker, then smoke-tests the live URL. It uses a GitHub production environment so each deploy gets a "View deployment" link. PR runs are still cancelled when superseded; master runs are not, so deploys never stop halfway. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
First item from Next steps: deploy automatically on every merge to
master.What it does
deployjob inci.yml. It runs only on pushes tomaster, aftercheckpasses:db:migrate:remoteapplies any new D1 migrations;run deploybuildsapps/weband runswrangler deploy;/api/health, the page and one/api/checkon the live URL.productionenvironment with URLhttps://cleanhashtags.didagou.workers.dev, so each successful deploy shows View deployment on the commit and PR and appears under Deployments.concurrency: deploy-production), and a run on master is no longer cancelled by a newer push. PR runs are still cancelled when superseded.Needed before merging
CLOUDFLARE_ACCOUNT_ID: already set.CLOUDFLARE_API_TOKEN: the owner must add it. The token needs Workers Scripts: Edit and D1: Edit. Without it the deploy job fails on the first merge, and nothing else breaks.Testing
pnpm lintpasses, and Prettier parses the workflow.🤖 Generated with Claude Code