-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: change maintenance mode info wording #37925
Conversation
452ece9
to
2f73260
Compare
2f73260
to
7727775
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That indeed looks like a better wording, thanks!
In maintenance mode the database is accessible and it's possible to execute other commands then maintenance:mode Signed-off-by: Daniel Kesselberg <[email protected]>
7727775
to
155ea6a
Compare
/backport to stable26 |
The backport to stable26 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable26
git pull origin/stable26
# Create the new backport branch
git checkout -b fix/foo-stable26
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26 More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
/backport to stable26 |
Summary
A customer brought to our attention that the message is misleading.
In maintenance mode the database is accessible and it's possible to execute other commands then maintenance:mode
The reason we changed the message was #20515.
I restored the old wording and added another line to make clear that some commands are unavailable.
TODO
Checklist