This repository has been archived by the owner on Oct 26, 2023. It is now read-only.
Fix/handle large repos #90
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scott-es
force-pushed
the
fix/handle-large-repos
branch
2 times, most recently
from
296b0ec to
a2cd556
Compare
scott-es
force-pushed
the
fix/handle-large-repos
branch
from
de122fa to
e6cc64d
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The primary method used by this tool to retrieve the GIT tree from each repository for the basis of comparison is via the Github API.
For sufficiently large repositories, though, Github truncates the API response. When a truncated Github response is detected when retrieving the GIT tree, this tool will fall back on using the local git if available and configured to perform a shallow clone of the repository's default branch in order to build the tree.
It will use /tmp to perform the git clone and then capture the output of git ls-tree -r
When this situation occurs, you will see the following in the console:
Large repo detected, falling back to cloning. This may take a few minutes ...
The truncated GIT tree response is described here. The last known limits are: 100,000 files or 7 MB of response data, whichever is first.