Make outcome of create-sibling-gin readily usable for a push data transfer
#6230
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
… transfer This change corrects and overrules a premature conclusion by git-annex on the non-availability of an annex at the GIN platform -- which is merely an effect of happening prior any branch availability on GIN. I decided to not pursue the alternative approach from datalad#6204 (comment) which could potentially be more expensive with no clear advantage. Fixes datalad#6209
Codecov Report
@@ Coverage Diff @@
## master #6230 +/- ##
===========================================
- Coverage 86.19% 64.27% -21.92%
===========================================
Files 323 323
Lines 41849 41845 -4
===========================================
- Hits 36072 26897 -9175
- Misses 5777 14948 +9171
Continue to review full report at Codecov.
|
bpoldrack
approved these changes
Nov 23, 2021
|
Thx! |
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.
This change corrects and overrules a premature conclusion by git-annex on the non-availability of an annex at the GIN platform -- which is merely an effect of happening prior any branch availability on GIN.
I decided to not pursue the alternative approach from #6204 (comment) which could potentially be more expensive with no clear advantage.
Fixes #6209