ENH: expose limit_to_ext param to control which files get written
#2
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
|
@rciric have you seen this PR? What do you think? |
|
closing because it's stale. Feel free to reopen. |
sappelhoff
commented
Jun 20, 2020
sappelhoff
commented
Jun 20, 2020
|
@oesteban could you have a look at this one as well, please? :-) |
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.
fixes #1
closes #4
This PR consists of three contributions. I suggest to click on the specific commits to review the diffs, because there are lots of cosmetic changes on top.
limit_to_extto stop hardcoding that onlynii.gzfiles get written. See: this diff: 79b8334.gitignorefile, see this diff: 49b3162Note: The PR preserves the previous behavior of datalad-osf (see 27c5f90).