Open acobster opened 5 years ago
Based on conversation with @philmprice, it sounds like the simplest option is to base the Netlify site on a docs
branch that only gets updated whenever there's a release. A GH Actions setup or similar could fast-forward the docs
branch automatically whenever a new release is created.
We don't want to ship docs to production that aren't included in an official release yet. The GH/Netlify shouldn't watch/build
master
directly; it should only trigger a build of the docs for new releases (tags).There may be a way to configure Netlify settings to do this through our Netlify account/project settings UI. If not, we'll need custom code a solution to either trigger a Netlify build directly on new releases or detect when there's no new release in our tooling and bail accordingly.