chore: Remove old theming migration steps as they are only needed once #43570
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
Signed-off-by: Julius Härtl <jus@bitgrid.net>
juliushaertl
requested review from
a team,
ArtificialOwl and
blizzz
and removed request for
a team
blizzz
approved these changes
Feb 14, 2024
skjnldsv
approved these changes
Feb 14, 2024
|
/backport to stable28 |
|
/backport to stable27 |
|
The backport to # Switch to the target branch and update it
git checkout stable27
git pull origin stable27
# Create the new backport branch
git checkout -b backport/43570/stable27
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick acda6b84
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/43570/stable27Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
Merged
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.
Those migration steps were introduced with Nextcloud 26 to migrate config values but are no longer required on subsequent major upgrades. On instances with a large user base the MigrateUserConfig can take a large amount of time to iterate over users that already have been migrated (50 min on a 3 million user instance I've seen)