-
Notifications
You must be signed in to change notification settings - Fork 37
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: improved branch cloning logic #32
Conversation
Lovely! As you've seen in the code comment above your change I actually wanted to do so. Thanks for tackling the special case. This is tested, I assume? :) |
Yep, I am now doing more testing. I Will let you know once I am done. |
@jgehrcke done testing, updated code to match the existing code style you are using. |
Thank you very much for this contribution, and for the splendid communication! Please come back if you have more ideas :). |
After a rework of the logic that checks if the data branch exists at the beginning of the script, the return code of `git ls-remote` is used in a check while `errexit` is active. Which means that the script will exit and the line checking the return code is never used. I might be missing something here, though, because I don't understand how this ever worked, but PR jgehrcke#32 was declared to be tested and working.
I might be doing something different than you did in your tests, but this code is not working in my install. |
I should not have relied on only that but also should have reviewed a little more carefully. Anyway, we get that sorted out :) Thanks everyone! |
Really sorry for that. Yep, I never saw the |
improved branch cloning logic. It now checks if the branch exists and uses git cli's
--single-branch
to improve cloning speed.