Proper version control for Libraries | Feature Requests

Proper version control for Libraries

under review

Darren Bennett

Currently when 2 editors of a library work on the same library at the same time one will lose their work in favour of the other if the other publishes first.
This means only one editor can work on a library in a team.
Within a team many editors need to be able to work on a library at the same time.
To achieve this the system needs proper version control. This includes the follwoing
Branching
Conflict resolution
Merging
I've never come across a team account that doesnt have this fearture tbh.

September 3, 2020

Philipp Nürnberg

If collaborative work as we know it from Figma is available, do we really need a version control with layer-based conflict solving? I mean, you have to manage the version control via a server, which means this feature is nothing for people who only works offline. Sure, ProtoPie offers a self-hosted server solution, but then you could work with the collaborative work again (from the self-hosted servers). If we would have collaborative work, for whom would this feature be an alternative?

Patricia (ProtoPie Team)

marked this post as

under review

Patricia (ProtoPie Team)

Merged in a post:

Git like parallel working on the same file

phng

Parallel working on the same file with git like merges, conflicts, etc.

January 3, 2022

Patricia (ProtoPie Team)

Merged in a post:

Version control comments

Darren Bennett

The ability to add comments to versions when they are uploaded to cloud

January 1, 2022

David Lee

Merged in a post:

Name versions

Nathan Maus

It would be very beneficial to name different versions in the cloud. I will run multiple user tests on the same prototype but the file has changed drastically through the versions. It would be good to know which version corresponds with which test was ran.

November 14, 2021

Patricia (ProtoPie Team)

Merged in a post:

Create a branch from existing ProtoPies

Rob Cleaton

Would be great to be able to create a Branch from someones existing ProtoPie so 1. Its crediting the creator, 2. We can share new ways to optimise with new features.

October 20, 2021

Ajay Karat

I agree, and would like to add in a bit more information, 
There is already an option to add comments a cloud update. The comment is the same for all versions, and gets carried over when the next version is uploaded to cloud. It would be a 'nice to have' feature where comments were tied to a specific version. 
I am unaware if this feature already exists in team, but the version I am using (individual plan) does not have this.

Jeff Clarke

Definitely a must have. This problem is compounded by the fact that there is no indication that the library is being edited by someone else. So an editor will most definitely get themselves into this situation without realising it until it's too late.

Simone Phillips

Yes! Good for knowing what has changed