Add support for sparse-checkout (v4 vbranch) #381
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Wanted to finally tackle kubernetes#54, I sidestepped the problem of how to handle the volume of flags that might be required by instead specifying a sparsecheckout file. The workflow as I've had has been... - Do a local sparse checkout, add the files you want ignored (or included on if you did a cone pattern https://git-scm.com/docs/git-sparse-checkout#_cone_pattern_set) - Grab your .git/info/sparecheckout file, and reserve it for later use with this new flag It's not quite as easy as specifying it all from a CLI, but I think it's a reasonable first pass. Here are some logs of it being run on https://github.com/SpencerMalone/logstash-output-prometheus: ``` test-repo % cat sparseconfig !/* !/*/ README.md test-repo % docker run --rm -d \ -v $(pwd)/git-data:/tmp/git \ -v $(pwd):/test \ docker.io/registry/git-sync:tag__linux_amd64 \ --repo=https://github.com/SpencerMalone/logstash-output-prometheus.git \ --branch=master \ --sparse-checkout-file=/test/sparseconfig 41494548dd64caf0ff8f7b75e4d3a86014cfaefc40ff31b14ba19accf99aa82f test-repo % ls git-data/db86200b1ab158ce9ad403d06de2301b15333601 README.md ``` As you can see, I ignored everything but the `README.md`, and sure enough only got that file in my final checkout.
k8s-ci-robot
added
the
cncf-cla: yes
thockin
changed the title
k8s-ci-robot
added
approved
stp-ip
approved these changes
Apr 26, 2021
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: stp-ip, thockin 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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Port #372 to v4 dev branch (@SpencerMalone)
Wanted to finally tackle #54, I sidestepped the problem of how to handle the volume of flags that might be required by instead specifying a sparsecheckout file.
The workflow as I've had has been...
It's not quite as easy as specifying it all from a CLI, but I think it's a reasonable first pass.
Here are some logs of it being run on https://github.com/SpencerMalone/logstash-output-prometheus:
As you can see, I ignored everything but the
README.md, and sure enough only got that file in my final checkout.