Hey guys, had a question. I've got four environments on SEED (dev, dev1 for another dev, staging, and prod). Now I know by virtue of SEED handling my stage and prod environments, the

sst.json

stage becomes irrelevant (or does it?). But my issue is rather on merging changes between the dev and dev1 branches where we're overriding the

sst.json

and bouncing back and forth between

dev

and

dev1

. How do I go about this or is there a better approach to this? Perhaps more insight as well into how SEED manages the sst.json file would be great.

{
  "name": "beta-courier",
  "stage": "dev",
  "region": "ap-southeast-1",
  "lint": true
}

Hey David, on the Seed side it's fairly straightforward. It does a `sst deploy --stage dev1". So it overrides the default stage in the

sst.json

. And

dev1

is the name of the stage on Seed. If dev1 is also the branch that's connected to that stage, then any git push to that branch should trigger a deploy to that stage and it'll use the above command. Does that help?