-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support caching repositories #235
Comments
I think it would be useful if it will not create to much problem for the user. |
@lindell admitted I didn't deeply think about this yet, but a first version could implement an algorithm such a the following, given a
I suppose there should also be a |
@Stephan202 So in that case, multi-gitter would still need to fetch from the remote. I guess this could speed up the process in some cases with very big repos and small changes 🤔 For those usecases it would indeed be useful. |
Indeed, we have a number of large repos that would benefit from this. (Currently we have a repository containing all our other repositories as submodules, with various operations performed using |
To give a little more flavour to the size of the problem: in our case (and I imagine many other companies) running |
I do agree that this is something that should be added! I will not have the time to look at this any time soon, but if you add it and create a PR, I'm happy to merge it 🙂 |
Hello!
When using
multi-gitter
I noticed that on every run the respective repos are always pulled.It would be great if this could be cached, to avoid long wait times to pull many repositories (especially when the entire org is specified).
The text was updated successfully, but these errors were encountered: