Uh oh!
There was an error while loading. Please reload this page.
Correctly drop the ownCloud migrations table - #7912
Merged
rullzer merged 1 commit intoJan 17, 2018
Merged
Conversation
Signed-off-by: Joas Schilling <coding@schilljs.com>
MorrisJobke
approved these changes
Jan 17, 2018
Codecov Report
@@ Coverage Diff @@## master #7912 +/- ##
=========================================
Coverage 51.23% 51.23% Complexity 24921 24921 =========================================
Files 1604 1604 Lines 94977 94977 Branches 1376 1376 =========================================
Hits 48661 48661 Misses 46316 46316
|
rullzer
approved these changes
Jan 17, 2018
rullzer
deleted the
bugfix/noid/correctly-drop-owncloud-migrations-table
branch
January 17, 2018 12:45
MorrisJobke
commented
Jan 18, 2018
Member
@nickvergessen Could you open the backport PR? |
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Fix#7699 (comment)