Feature Request: Add Additive-Only Sync Mode for Shared Prismic Repositories

Developing with Prismic
,
1

Hi team,

After upgrading slice-machine-ui from 0.5.2 to 2.21.2, we noticed a major change in how Slice Machine handles synchronization with Prismic repositories.

Our setup consists of multiple projects that push slices and custom types to the same Prismic repository.

With the older 0.5.x versions, Slice Machine behaved in a more additive way:

  • new local slices/custom types were pushed

  • existing remote models that were not present locally were ignored

  • no deletion/removal changes were suggested

This worked very well for shared repositories across multiple projects.

After upgrading to 2.21.2, Slice Machine now actively compares the local filesystem with the remote repository state and detects remote-only models as changes or potential removals, even when nothing was modified locally.

Would it be possible to introduce an optional "additive-only" sync mode in slice-machine-ui?

For example:

  • only create/update local models

  • ignore remote-only slices/custom types

  • never suggest deletions for models missing locally

Something like:

{
  "syncMode": "additive"
}

or:

{
  "ignoreRemoteOnlyModels": true
}

This would greatly help teams that intentionally share a single Prismic repository across multiple applications/codebases.

Thanks!

2

Hi @marlon_kerstens ,

Thanks for sharing this feature request, I can definitely understand the value of having an “additive-only” sync mode for shared repositories.

Being able to safely push only new changes without overwriting or deleting existing content would help reduce risk in collaborative workflows and multi-repository setups.

The last update from the team on this topic was here in another thread:

Really appreciate you taking the time to outline the workflow and explain the challenges you're running into.