-
Notifications
You must be signed in to change notification settings - Fork 28
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
Shallow clone variants #283
Conversation
This commit splits the CloneOrOpenRepo function to two utility functions to avoid code duplication and expose the options of the clone call. Signed-off-by: Adolfo García Veytia (Puerco) <adolfo.garcia@uservers.net>
mmmh 🤔 |
This commit split the core of the functionality of the CloneOrOpenRepo to a utility function to make it reusable from functions requiring different git options. Signed-off-by: Adolfo García Veytia (Puerco) <adolfo.garcia@uservers.net>
This commit adds Shallow* variants to our clone functions. The goal of these is to enable faster cloning of large repositories. Signed-off-by: Adolfo García Veytia (Puerco) <adolfo.garcia@uservers.net>
Found the error. Thank you tests for doing your job 😸 |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, puerco The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds
Shallow*
variants to our clone functions. These work exactly as their counterparts but perform a shallow (depth 1) clone of repositories to work with large repositories at HEAD more efficiently.The new functions are:
git.ShallowCloneOrOpenRepo()
git.ShallowCloneOrOpenGitHubRepo()
git.ShallowCleanCloneGitHubRepo()
Note that this PR has many lines but at its core, it is the same logic just broken into ever more specific utility functions to reuse our code. The outward-facing functions just invoke the internal ones with a different options set. Roughly:
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
/assign @saschagrunert @cpanato @xmudrii
Does this PR introduce a user-facing change?