Clean up temporary clone paths by default #113
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #98 .
These changes allow git-xargs to clean up the temporary file paths where it clones repositories. By default, git-xargs will now delete the paths after processing the repo. If you wish to preserve your local clones, pass the new
--keep-cloned-repositories
flag.TODOs
Read the Gruntwork contribution guidelines.
Release Notes (draft)
By default, git-xargs will now delete the temporary file paths where it clones your repositories in order to run commands on them. This should help prevent git-xargs from taking up too much space. If you wish to preserve local clone paths going forward, pass the new
--keep-cloned-repositories
flag.Migration Guide