Sometimes you’re doing a lot of small iterative changes in a CMS which you need to publish to work with the latest content locally. Those can burn a lot of build minutes needlessly. Would be cool if there was a way to temporarily disable build hooks under deploy settings in such cases.
Hey @Janosh, thanks for writing in. Have you checked out our docs on
[skip ci]? This may help you accomplish what you want:
Here’s a description of what this would look like with Netlify CMS:
Hi @jen, I do know about
[skip ci] but it’s only for skipping builds triggered by changes that involve a commit message. In my case, the builds are triggered by a Contentful web hook and don’t have an associated commit message.
I was hoping for a button in the deploy settings for temporarily disabling all or individual hooks as indicated in the screenshot below.
Ah, thanks for clarifying! We’re working on a feature like this and will share updates here when we have them
Great to hear that, looking forward to those updates.
+1 for this feature. Any update on this so far?
You do now have the ability to stop builds and then reactivate them when you’re ready