There is nothing preventing you from saving versions of the same model or data file in more than one repository — for example by changing to a branch in another repository when saving from the Save or Export window. Doing so, however, will make it difficult to track how an item has evolved over time via its different versions, as well as make it harder to reason about the Access Control of the item. You may be better off saving a new item from the existing item using Save as New () in the Save or Export window — in this way, you keep items within their respective repositories, while still being able to track how a new item in one repository evolved from an existing item in another. See also Splitting a Model Version History in Two.
|
1
|
Write the name of the new repository in the Name field.
|
2
|
Write the name of the initial, default, branch in the Default branch name field — see Default Branch.
|
3
|
4
|
You can set up permissions for the new repository in the Permissions field. This field is only shown if connected to a server database via a Model Manager server. See Granting Permissions.
|
5
|
Click OK to add the repository.
|