We have two engineers building a Workshop Module together, but often at overlapping times. What are the best practices for two or more teammates to work together toward building a single Workshop Module? Is there branching available in Workshop? How can we prevent any new saved changes from over-writing a teammate’s work? Thanks!
1 Like
This case could occured also at our office.
In addition I face also case where Branching in workshop could be useful : demonstration of to différents solutions and selection of the best one.
Best regards.
One approach is to have multiple workshops embedded into a master workshop - then you can work on the respective parts
@100hamilton , thanks for the question!
Branching is indeed the intended solution here and became a beta feature available in Workshop earlier in 2025: https://www.palantir.com/docs/foundry/foundry-branching/overview. If you’re interested in helping with the beta test, please reach out to your Palantir support rep to have this enabled on your instance.
With branching, each Workshop builder can modify a Workshop module on a branch and then can merge their specific changes back to main when ready. Workshop’s implementation of branching also supports rebasing a outdated module on a branch to incorporate the latest changes from main, and this feature in particular unlocks collaborative building in a first-class way for the first time.
2 Likes
Thanks for the quick response, from the legend himself no less!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.