Fix GH Clones Needing Explicit Directory Name #10
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.
What is this PR?
Why is this PR needed?
Cloning from GH via GitPython places the repository root in the target directory, it does not create a new directory with the repository name and insert it into the target directory.
This was causing the
-g
option to flag submissions as incorrect because the top-level folder did not match the expected naming pattern.What does this PR do?
Repos that are fetched from GitHub now have their name inferred, and are relocated to a temporary directory with this name.
How has this PR been tested?
Is this a breaking change?
Checklist