-
Notifications
You must be signed in to change notification settings - Fork 23.9k
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
Fix fallback to unshallowing shallow clone #70252
base: devel
Are you sure you want to change the base?
Conversation
Can you add a test to show what this is solving, and a changelog fragment? |
@elmeriniemela Are you still working on this? Thanks. needs_info |
@Akasurde Not really, unfortunately I don't have the resources to develop the tests related to this. Feel free to take this issue further. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This needs a rebase for the CI to pick up the branch. |
@elmeriniemela This PR is waiting for your response. Please respond or the PR will be closed. |
Hi, the comment in the code explains why depth argument is needed when 'refspecs' variable is empty. However the condition adds it only when "if refspecs" when it should be "if not refspecs". So there is clearly a contradiction with the intention of the developer (expressed in comment) and the actual code. And this causes an error as explained in the PR description. |
Currently git may not find the correct commit with depth=1000000 and shallow clone, caused by an error in the final fall back if clause. The comment in the if clause is correct, just missing a 'not' operator for the comment / behavior to work.
c2902a3
to
f6c30fe
Compare
Currently git may not find the correct commit with depth=1000000 and a shallow clone, caused by an error in the final fall back if clause. The comment in the if clause is correct, just missing a 'not' operator for the comment / behavior to work.
ISSUE TYPE
COMPONENT NAME
git
ADDITIONAL INFORMATION
Reproduce steps: