Fix: import a non-empty data-folder on first-start for github/gitlab storage backend#352
Merged
Fix: import a non-empty data-folder on first-start for github/gitlab storage backend#352
Conversation
Codecov Report
@@ Coverage Diff @@
## main #352 +/- ##
=======================================
Coverage ? 80.44%
=======================================
Files ? 51
Lines ? 2685
Branches ? 437
=======================================
Hits ? 2160
Misses ? 430
Partials ? 95
Continue to review full report at Codecov.
|
…storage backend Before it assumed the remote branch already existed, and would use that as template. But if that isn't the case, import the current data folder, and create the remote branch. This is mostly meant to allow end-to-end testing, which has already some content in the data-folder.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Before it assumed the remote branch already existed, and would
use that as template. But if that isn't the case, import the
current data folder, and create the remote branch.
This is mostly meant to allow end-to-end testing, which has
already some content in the data-folder.