[gpuCI] Forward-merge branch-0.19 to branch-0.20 [skip ci] #1548
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
Got rid of the GIT_SHALLOW setting since it should not be enabled by default. Authors: - Alex Fender (https://github.com/afender)
|
FAILURE - Unable to forward-merge due to conflicts, manual merge is necessary. Do not use the |
Merge branch-0.18 into branch-0.19
Codecov Report
@@ Coverage Diff @@
## branch-0.20 #1548 +/- ##
==============================================
Coverage ? 60.98%
==============================================
Files ? 73
Lines ? 3217
Branches ? 0
==============================================
Hits ? 1962
Misses ? 1255
Partials ? 0 Continue to review full report at Codecov.
|
BradReesWork
approved these changes
Apr 26, 2021
rlratzel
approved these changes
Apr 27, 2021
rlratzel
added
improvement
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.
Forward-merge triggered by push to
branch-0.19that creates a PR to keepbranch-0.20up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge.