Push only one Slice/Change to Prismic

Developing with Prismic
,
29

This isn't the solution either and isn't why this was implemented.

I totally agree, and I'm just pointing out one of the difficulties here, I'm not suggesting pushing everything is the solution.

I'm not involved in decision-making or designing on this, but when the team implements a solution, like the checkboxes you suggested above, we'll have to take into consideration warnings about changes, the local source of truth and changes between git branches in your workflow.

Thanks again for your feedback

31

Is there any resolutions on this?

32

Hi @across-platforms,

Thanks for checking in. We don't currently have any update on this feature. If/when we do, we'll post it here so everyone who's shown interest is made aware of it :slight_smile:

33

+1 here, terrible DX when multiple devs working in slicemachine on different branches, copying slicemachine schema from other branches is not a fix for this

would be so great to have a simple checbox on every change and be able to push what I want to push

4 Likes
34

granular control over individual slice push would be extremly useful / necessary.

we’ve invested heavily in Prismic and the slice machine and the current status (push all or nothing) is slowing down our development and deployments.

I appreciate designing such feature in a complex system is often not as easy as it looks on the surface.

thanks for considering!

3 Likes
35

Hey everyone, thanks a lot for sharing your thoughts here.

We’re aware of these issues, especially the pain when multiple developers are working on different branches.

These topics are already on our radar, and we plan to work on improvements around that.

I don’t have a specific timeline to share yet, but it’s definitely something we want to address

Really appreciate the feedback :folded_hands: