M-Pixel Posted October 10, 2017 Report Share Posted October 10, 2017 Here's the scenario: Foo has repository Bar on GitHub SuperCow has repository Baz on GitHub, which is a fork of Foo/Bar I want to, in turn, fork Baz as a Plastic SCM repo, while retaining the ability to merge and cherry-pick from Baz and Bar, and the ability to contribute to Baz. After doing a bit of reading, my intuition is that I should create a repository where the main branch is synced with Foo/Bar, a child branch is synced with SuperCow/Baz, and a subsequent child branch that I use for development. The documentation doesn't cover any scenarios that involve multiple Git repositories, fork or not, so I figure there is probably something wrong with my suggested approach, or, at the very least, gotchas that I should be aware of. Link to comment Share on other sites More sharing options...
M-Pixel Posted October 11, 2017 Author Report Share Posted October 11, 2017 I've discovered that Git Sync works on a repository level, not a branch level. So it's impossible to sync simultaneously with multiple Git repositories. The solution that I intend to use now is to migrate updates from upstream repos to fork repos using a local intermediary Git repository, while syncing Plastic only with the leafmost Git repository. Link to comment Share on other sites More sharing options...
calbzam Posted October 18, 2017 Report Share Posted October 18, 2017 Yes, I'm afraid GitSync only allows to sync a specific Plastic and git repository. https://www.plasticscm.com/documentation/gitsync/plastic-scm-version-control-gitsync-guide.shtml In the following link we explain the different options to acess git repos from Plastic and vice versa: https://www.plasticscm.com/features/plasticscm-for-git-users.html Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.