Ensure workspace class is persisted #11957
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
Furisto
force-pushed
the
fo/ensure-persist
branch
2 times, most recently
from
f1e9203
to
6786608
Compare
Furisto
force-pushed
the
fo/ensure-persist
branch
from
6786608
to
dc46b24
Compare
roboquat
added
release-note-none
and removed
do-not-merge/release-note-label-needed
labels
andrew-farries
approved these changes
Aug 9, 2022
roboquat
added
deployed: webapp
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
Ensure that the workspace class is persisted regardless of whether new or old workspace classes are used.
Related Issue(s)
Fixes ##11956
How to test
Open a workspace and check in the database that the workspace class is there
Release Notes
Werft options: