[SDK] arv-copy automatically creates new repository(ies) on the destination cluster
arv-copy currently checks out a destination repository and pushes branches to it. Now that Arvados lets users create their own repositories, it should take advantage of this feature.
Engineering to determine:
- Should arv-copy still support the "push to one repository" mode?
- Should arv-copy create one repository? Or one repository per source repository?
- If arv-copy supports multiple modes, what's the default mode, and how does the user select between them?
- How are names for the destination repository(ies) determined? If arv-copy has a mode where it creates multiple destination repositories, does the user have any control over their naming? How is that specified?
#2 Updated by Brett Smith over 4 years ago
- Subject changed from [SDK] arv-copy uses git over http and creates new repositories. to [SDK] arv-copy automatically creates new repository(ies) on the destination cluster
- Description updated (diff)
- Category set to SDKs
The "copy over HTTPS" story exists separately as #6605. Dedicating this story to the other half, "create new destination repositories."