Problem/Opportunity
Repo has introduced a submanifest feature. This feature allows users to include in their manifest another git repository, containing a manifest .xml for that they want to include as part of the project.
SC will need to handle this with it's cloning and branching commands.
Proposed Solution
I believe we should treat all submanifests as READ_ONLY. Therefore, SC cannot write new revisions to the submanifests and does not need to branch or push them. This will allow people to use the submanifest for fixed versioned manifests without having multiple project competing to push commits back to shared submanifest projects.
Acceptance Criteria (Optional)
No response
Additional Notes (Optional)
No response
Problem/Opportunity
Repo has introduced a submanifest feature. This feature allows users to include in their manifest another git repository, containing a manifest .xml for that they want to include as part of the project.
SC will need to handle this with it's cloning and branching commands.
Proposed Solution
I believe we should treat all submanifests as READ_ONLY. Therefore, SC cannot write new revisions to the submanifests and does not need to branch or push them. This will allow people to use the submanifest for fixed versioned manifests without having multiple project competing to push commits back to shared submanifest projects.
Acceptance Criteria (Optional)
No response
Additional Notes (Optional)
No response