refactor: strip existing project when adding it to an organization #3726
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
shreddedbacon
force-pushed
the
refactor-add-existing-project-to-org
branch
from
6566383
to
e961cef
Compare
shreddedbacon
force-pushed
the
refactor-add-existing-project-to-org
branch
from
e961cef
to
0bf18e1
Compare
tobybellwood
approved these changes
Jun 26, 2024
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.
General Checklist
Database Migrations
There exists a condition when adding an existing project to an organization that could result in a project and any groups it has being left in a disconnected state. This refactor is to make sure that the project and any access it previously had is stripped entirely when adding the project to the organization. Effectively it would appear as a fresh project (still retaining all of its environments etc. though)