-
Notifications
You must be signed in to change notification settings - Fork 187
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
Re-instantiate non-optimized clone fallback #1126
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think it would be great if we simply could make gitCheckout
figure this out by itself, as this would concentrate the logic in a single place. But left this as an exercise.
0fc40c1
to
7d392b8
Compare
f693d7c
to
7d392b8
Compare
This adds a bit back which got removed in 69f567b, as there are reasons for the controller to perform a non-optimized clone. However, we always want to attempt the optimized version first without it being put behind a feature gate. Which was the original intent of the referenced commit. Signed-off-by: Hidde Beydals <[email protected]>
3cc2f27
to
b79fe22
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @hiddeco 🥇
This is required because the test fails with Git >=v2.41.0 due to changes to commands used by the Git test server. Causing the server to return an error when cloning an empty repository, instead of yielding an empty object. Signed-off-by: Hidde Beydals <[email protected]>
b79fe22
to
60571c0
Compare
This appears to actually be related to go-git/go-git#802 |
I would concur with the above. And would use the pseudo version from master until a go-git release is cut - which will take a few weeks. |
This adds a bit back which got removed in
69f567b, as there are reasons for the controller to perform a non-optimized clone.
However, we always want to attempt the optimized version first without it being put behind a feature gate. Which was the original intent of the referenced commit.