Every time the monorepo's split command is called, repositories re-clone. For instance, if my project contains 100 sub-repo, re-cloning every time is huge.
Currently, there's no workaround and including a --clean options to monorepo's workflow commands is necessary if the developer decides to choose a re-clone. More so, the --only option already provided is helpful as it allows re-clone support for a single or list of repositories.
Motivation and context
Making monorepo's workflow commands work faster and reduce cost of bandwidth for better developer experience.
This PR closes #15
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Deprecation (un-wanted or renamed functionality that should be removed)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
PR checklist
[ ] My change requires a change to the documentation.
Discussion
Every time the monorepo's split command is called, repositories re-clone. For instance, if my project contains 100 sub-repo, re-cloning every time is huge.
Currently, there's no workaround and including a
--cleanoptions to monorepo's workflow commands is necessary if the developer decides to choose a re-clone. More so, the--onlyoption already provided is helpful as it allows re-clone support for a single or list of repositories.Motivation and context
Making monorepo's workflow commands work faster and reduce cost of bandwidth for better developer experience. This PR closes #15
Types of changes
PR checklist