Would it be possible to have one branch do multiple deploys?
For example: Netlify is linked to a Github repo. All code is merged into the master branch of that repo. The Netlify config for that repo has two different URLs -
example.com and either
staging.example.com or just use a consistent netlify url for staging.
The deploys to the main site can be locked just like normal, but the deploys to the staging branch are continuous.
- All code is merged to master, reducing merge conflicts and reducing the need for a persistent staging branch (which usually then has to get merged into master later on to deploy)
- The staging branch+website is always the latest code, greatly simplifying QAs’ jobs by not having n number of different netlify deploys to go look at, and devs’ jobs by integrating sooner with other dev’s code
- Deploys to prod website can be manual (by unlocking the deploy and then locking again)
 from a very naive perspective, it seems that netlify maybe already has the core functionality to enable this, it would just be rearranging it in a different way. But software is hardly ever that easy
But this would be a huge boon to devs/companies that do trunk-based development, which currently with netlify is a pain and a blocker in many ways. We’ve considered moving off of netlify because of the difficulty of trying to get a good trunk-based development workflow going.