Right now, the Wrangler github actions step deploys a worker whenever a deploy to feature/* or develop or prod happens.
This is a big problem
It means that any changes in the worker/index.js file will result in a change to production while testing out the code in a feature/* branch deployment
The likely fix is to have different (environment-scoped namespaces and workers set up for testingnear.me (optionally feature/* deploys can be sent here) vs. devnear.me vs meetnear.me
Right now, the Wrangler github actions step deploys a worker whenever a deploy to
feature/*ordeveloporprodhappens.This is a big problem
It means that any changes in the
worker/index.jsfile will result in a change to production while testing out the code in a feature/* branch deploymentThe likely fix is to have different (environment-scoped namespaces and workers set up for
testingnear.me(optionally feature/* deploys can be sent here) vs.devnear.mevsmeetnear.me