Our site: sdk.operatorframework.io
Our workflow for creating versioned documentation is that we create a new release branch, and then build our assets, and then publish the docs. A requirement for this workflow is that the new branch must be on the same git commit as the commit used to build the assets.
On Netlify, our process is:
- Add the not-yet-existent branch Build&Deploy → Branches → individual branches
- Create the new branch. On the Netlify side, this causes Domain → Branch Subdomains → “No more branches” to change to an option to add the new branch/subdomain.
If the individual branch is typed incorrectly, or added after the creation of the new branch, we are in a state where we cannot modify the branch, nor get netlify to add the option for a new branch/subdomain.
None of our branches are currently in a broken state, so a one-off fix is not required, but going forward, is there a way to trigger Netlify to look for a new branch rather than wait for the branch commit to change?