Publish all changes

[silkstudio]

Is your feature request related to a problem? Please describe.
I'm using a Sanity hook to trigger a Netlify build when a Sanity doc is updated but have found that if I'm editing multiple docs and then publish them successively, it will trigger multiple builds.

Describe the solution you'd like
It would be super helpful if you could edit multiple docs and then 'publish all changes' in one go rather than having to do it for individual docs.

Describe alternatives you've considered
For the moment just doing it individually and potentially spacing changes so as not to trigger multiple successive builds.

Additional context
Apologies if something like this already exists, I wasn't able to find much from a quick scan through previous requests but am happy to be educated!

[marijoo]

The option to debounce triggers or to publish all documents at once would be super helpful – both ecological and economically. ✌️

[janhoogeveen]

Additionally, grouping these into versions would be even better It seems like a logical conclusion to grouping changes!

How Prismic does this: https://user-guides.prismic.io/en/articles/778358-what-is-a-release

[PutziSan]

Is there a workaround to publish all, e.g. via HTTP API or cli?

[tobijafischer]

Grouping multiple changes into releases sounds really convenient.

[logemann]

This is a serious drawback currently. Now i am doing 200 publishes which will take me forever

[grountish]

this would be awesome

[AmodeusR]

Nothing yet? It gets really tedious to publish each change at a time.

[miked-known]

Any movement on this ? This would be a killer feature to have 🙏

[ozymandias547]

This is a necessity. If anyone knows of a plugin that handles this, please let us know.

[sitek94]

+1 it would be really nice to have such feature, especially when making atomic changes to multiple documents

[olivierolivier]

+1 Makes a lot of sense both in terms of usability for editors and to decrease the carbon footprint of a website/app.

[JayBox325]

I built a platform that had tags. Now I'm building the tags pages to display content associated with that tag, however, I've got a shed-load of tags with a required slug field that I now have to manually go and update. For the future, it would be great for a document section "mass actions" option, to mass delete, mass publish, mass unpublish etc.

[RaynoldVanHeyningen]

any information regarding this? things started of fine during development phase, but now in production, the amount of documents is growing steadily larger. Recently developed a new feature, which requires me to republish all these documents to trigger a webhook. Having to do this now one by one, is becoming a big time-wasting task

[kitsbits]

This is a very common-sense and needed feature. Leaving a comment to make sure this thread stays open. Please do this!

[artmen1516]

This is a really important feature, please implement it, could be responsible to change to another CMS that has this...

[droplab]

Agreed, this is a crucial feature. Is this even on the roadmap? Is there an ETA?

[achyuta116]

While testing out a website, it'd be convenient to have this feature to group and publish changes, has this feature gotten any attention?

[grantimbo]

Currently in the process of transitioning from Prismic to Sanity, and this is the only feature that's missing so far. Hoping to see this feature implemented on Sanity.

[yornaath]

Yes this is needed 👍

[Maxframe]

I would indeed appreciate this time-saving feature

[LucaArgentieri]

What's new? It would greatly reduce the build time.

[farmtopeople]

+1 from our whole company. We need this feature!

[alivault]

+1. Needed this feature yesterday. I had to make changes to a bunch of items and there wasn't a way to batch publish all at once, so I had to publish each one individually and it would trigger a build each time.

[JayBox325]

The silence form the Sanity team here, on social media and in the official slack is deafening. If fixing this issue was a major task due to how their content model works or something like that, I'd rather they told us that instead of ignoring it. It's a pretty big part of the platform.

[LucaArgentieri]

I achived a similar result with the Netlify Deploy plugin

I never tried with Vercel but this should be the same

[michaelcpuckett]

+1 Need this for triggered pushes

[Jay-Ferguson]

I feel like this should be a built in feature for any modern CMS. I thought a VC backed project like Sanity would have had this a long time ago.

[awbranch]

I need a this too. Any update?

[faraazm]

Seriously? We don't have this yet?

[kelenakamura]

so using the netlify deploy plugin manually isn't enough? just don't trigger deploys on publishing docs, only deploy when you manually trigger it via the netlify deploy plugin?

[marijoo]

so using the netlify deploy plugin manually isn't enough? just don't trigger deploys on publishing docs, only deploy when you manually trigger it via the netlify deploy plugin?

You mean the official plugin? That one wasn’t touched for two years and seems to not even be compatible with Dashboard v4.

[kelenakamura]

yes was referencing the comment from Apr 22. wondering if that workflow worked for anyone.

[marijoo]

Just found this alternative which seems to be working on the first sight: https://github.com/jclusso/sanity-plugin-netlify

[kmelve]

Hi folks! We haven't done a great job being present here on GitHub, but we have a solution for you all in the works: Content Releases. We are working on the public beta as we speak.

Alternatively, as proposed by some of you, installing or adding an affordance that lets Studio users hit a build trigger can also work.