Hi, @ramono. It all does work how you want it to work, if you don’t do what you did (making a branch deploy the production deploy).
Normally that branch subdomain auto-updates to show the most recent deploy of that branch. The only reason it did not is because you had locked in a previous deploy of this branch.
You made the
beta branch your production branch when you clicked the “Publish deploy” button for a deploy of that branch (
beta). The “Publish deploy” button locks all deploys of the site to that exact deploy. If you do this for a branch subdomain, it also locks the branch subdomain to that deploy.
The “Publish deploy” button is designed to override the normal auto-publishing of the branch. The button you clicked says, “Don’t auto-update anymore. Keep the site locked to this exact deploy.” The branch subdomain doesn’t update because that button says “don’t auto-update”.
One way to fix this would be to do the following.
- Go to any production deploy, for example here: https://app.netlify.com/sites/eager-franklin-dabe13/deploys/60ac2476129e63000870fbb7
- Click the “Publish deploy” button.
The deploy above (
60ac2476129e63000870fbb7) is a production branch deploy, not a
beta branch deploy. If you publish the production branch deploy (not the
beta branch) then the beta branch subdomain will behave as it normally would. You will have removed the lock on the
beta branch and auto-publishing of the branch subdomain will work normally again.
If there are other questions about this, please let us know.