You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just found this issue while trying to find out whether netlify have built-in support for release only on tags.
Apparently, they don't which I think is mad.
But my workaround for pydantic is to setup netlify to deploy a fictional branch foobar (to avoid netlify auto-deploying), then manually deploy from CI when a tag is created, see here for the makefile command, and here for the travis setup.
I think that's more elegant than manually pushing to a branch.
I rolled back to the earliest good deploy of v5.2.0 (deploys were failing around the release, but this was fixed sometime after). That's eeccd05 if we want to be specific.
I disabled auto-publishing of the production branch (master)
I didn't change our deployment preview settings.
I created an incoming webhook on netlify. These only trigger a build against a selected branch. I selected master.
I created an outgoing webhook on GitHub to be triggered whenever a GitHub "release" event occurs.
This doesn't work, unfortunately, because of the disabled auto-publishing.
Netlify's API has an endpoint to lock/unlock auto-publishing, however. I'll see what I can do with this. If I can't figure it out, we'll just have to create a branch for doc publishing, and update that branch every time we tag a release (or automate it).
OK, yeah, in order to make that happen properly I'd need to either create a GitHub app or action. The former is more work than I'm willing to do atm (though using Probot would be a great place to start), and the later is still in private beta, so whatever. Branches it is for now.
I'll configure netlify to only publish, say, the mochajs.org branch, and keep that updated when we release.