Often times there are minor changes to components of our design system that are necessary for designers to move forward with their work, but we have a few design system designers working on other changes within the same file. The Auto-save is constantly updating the file so that when it’s time to publish the fix for the designers, all of the other changes come along with it—even if they might not be ready to be deployed. I understand that designers can cherry-pick which things to update, but in reality, most aren’t going to go through one-by-one and see if it breaks their design.
I’d love to be able to check which updates I’m publishing (similar to staging changes/committing changes with git). Then if there are non-breaking changes, but critical blockers for designers, I can publish those and not the rest of the library updates.
One blocker from this would be the way the publishing modal is designed—right now you simply see ‘Changed,’ which doesn’t help me a ton, especially if I’m using nested components. I wish there was a better description of what the changes were.
This is a terrible example, but hopefully, my point is clear.
Am I overthinking this? Is anyone else running into this same issue or have better process management?