Finish removal of Organization short name - Part 2#5187
Merged
dorner merged 3 commits intoMay 23, 2025
Conversation
6 tasks
dorner
approved these changes
May 9, 2025
Collaborator
dorner
left a comment
dorner
left a comment
There was a problem hiding this comment.
All good - let's move this to Draft status so we don't accidentally merge.
Collaborator
|
@dorner -- Is there any reason we wouldn't just go ahead and merge this now? |
dorner
approved these changes
May 23, 2025
Collaborator
|
It was blocked on #5186 which is now merged. |
Contributor
|
@jp524: Your PR |
GiovannyCordeiro
pushed a commit
to GiovannyCordeiro/human-essentials
that referenced
this pull request
Jun 6, 2025
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
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.
Resolves #5167
Description
Contains migration to remove column
short_namefrom Organization.According to Strong Migrations docs, this PR should be deployed only after #5186 has been deployed.
Only the last commit of this PR is needed. The first nine are included in Part 1. I included them here too for CI to pass and because I can't set my branch as the base repo (don't have collaborator permissions). I'll rebase on main once Part 1 has been merged
Type of change
How Has This Been Tested?
See #5186
Screenshots
n/a