Professional membership migration#8736
Merged
Merged
Conversation
f4d6f76 to
b00c162
Compare
c1a5131 to
a628b09
Compare
af21dd2 to
104d13a
Compare
Collaborator
|
🙋♂️ I think something happened here with the split, and changes from the first bit ended showing here in the diff too. Guess this will need a revisit after releasing the first PR! |
104d13a to
0fb51b3
Compare
|
Review app https://teaching-vacancies-review-pr-8736.test.teacherservices.cloud was successfully deleted |
a628b09 to
49a8bc5
Compare
0fb51b3 to
38425b4
Compare
63f2745 to
4b75c55
Compare
4b75c55 to
f701d31
Compare
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
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.
Trello card URL
Changes in this PR:
Migration for removing profile professional body memberships
Checklists:
Data & Schema Changes
If this PR modifies data structures or validations, check the following:
If any of the above options has changed then the author must check/resolve all of the following...
Integration Impact
Does this change affect any of these integrations?
User Experience & Data Integrity
Could this change impact: