Merge 3.1.x into 3.2.x #4820
Merged
Merge 3.1.x into 3.2.x #4820
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
Fix Schema::getTableNames()
Fix renaming upper-cased SQLite columns
1 task
derrabus
approved these changes
Sep 28, 2021
greg0ire
approved these changes
Sep 28, 2021
|
@derrabus we normally don't merge the "merge up" pull requests since there's already a merge commit. GitHub allows pushing the approved and built merge commit upstream even if the target branch is protected. A benefit of doing that is that one can create multiple "merge up" pull requests at a time (e.g. |
|
I see, thanks for explaining. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
No description provided.