Feature requests - what do you already love, what could be better?

Features
113

I guess I am not understanding what is not possible in that workflow with our existing tooling:

  1. you configure your repo with a netlify.toml that will apply for the 2 sites you link it to. It sets things like environment variables, build command, etc.
  2. on the stage site, you have us build every commit automatically. You can see work in progress at reliable URL’s like feat-1234–mystagesite.netlify.app, and you can see the production build at its URL which you could either set a sitename like “beta.yourdomain.com” for, or use the netlify site directly (https://yourstagingsite.netlify.app).
  3. on the prod site, you have deploys either turned off completely or instead use the locked deploy feature to prevent unwanted publishes. You’d also have builds for all non-production branches turned off, since you don’t need to see a second copy of those builds on the short lived branches on this second site.

Does that sound feasible, and if not, what feels bad about it?