You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, each run of git-xargs clones the desired repository into the system's temporary folder. This is true for each time you target a repository running git-xargs.
Here is an example from my machine after experiencing with git-xargs for a couple of days (MacOS 12.5.1):
As one can check, there are multiple instances of the same repository, which can lead to extreme sizes after using git-xargs for a long time.
Describe alternatives you've considered
I see a couple of alternatives to resolve this issue:
Clean up the repos after each execution from git-xargs. Add a optional flag --keep-cloned-repositories to keep the repo for debugging purposes.
Make the CLI check if the repositories that need cloning are not already present in the filesystem. If they are, perform a git pull instead of cloning the repository again. This one will probably need changing quite a lot in the code, but can lead to improvements on performance, specially when dealing with large repositories.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
Currently, each run of
git-xargs
clones the desired repository into the system's temporary folder. This is true for each time you target a repository runninggit-xargs
.Here is an example from my machine after experiencing with
git-xargs
for a couple of days (MacOS 12.5.1):Command output
As one can check, there are multiple instances of the same repository, which can lead to extreme sizes after using
git-xargs
for a long time.Describe alternatives you've considered
I see a couple of alternatives to resolve this issue:
Clean up the repos after each execution from
git-xargs
. Add a optional flag--keep-cloned-repositories
to keep the repo for debugging purposes.Make the CLI check if the repositories that need cloning are not already present in the filesystem. If they are, perform a
git pull
instead of cloning the repository again. This one will probably need changing quite a lot in the code, but can lead to improvements on performance, specially when dealing with large repositories.Additional context
N/A
The text was updated successfully, but these errors were encountered: