migrate: move user group migration to latest #3012
Merged
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
m17ch
previously approved these changes
May 12, 2023
m17ch
approved these changes
May 12, 2023
cmarquis
approved these changes
May 12, 2023
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.
Description:
The Slack user group migration was mistakenly left out of order.
Which issue(s) this PR fixes:
Fixes a problem where instances tracking master will miss the migration (resulting in the user group feature being broken).
Out of Scope:
Since this wasn't in a release, and the migration in question is safe to run multiple times, no action will be taken to clean up old entries (
20230320111353-slack-ug) fromgorp_migrations.