Non-production branch deploy command

I'm starting to use workers as I'm adding workflow support to an application I'm serving with pages. I'm working on getting prod and no-prod environment alignment and I'm seeing some oddities when i'm deploying the worker for a PR. it seems to be running the "Non-production branch deploy command" which I have set to a pnpm script that runs this

wrangler deploy --config workers/sync/wrangler.jsonc -e preview workers/sync/index.ts

wrangler deploy --config workers/sync/wrangler.jsonc -e preview workers/sync/index.ts

and passes the "-e preview" to send this to the preview environment which appears to be a separate worker. This command works when I run it locally but doesn't seem to be doing the right thing when it's running via the github integration when I push code up... Any one have any experience with this and/or ideas?

Cloudflare Developers•7mo ago

jame

Non-production branch deploy command

wrangler deploy --config workers/sync/wrangler.jsonc -e preview workers/sync/index.ts

wrangler deploy --config workers/sync/wrangler.jsonc -e preview workers/sync/index.ts

Non-production branch deploy command

Similar Threads

Non-production branch deploy command

Similar Threads

Similar Threads

Similar Threads