-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Improved timeout_richDocuments
#11512
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
Conversation
|
master-IT test failed: https://www.kaminsky.me/nc-dev/android-integrationTests/8243-IT-master-05-26 |
Didn't read very well before. Signed-off-by: Hammy Havoc <hammy@splitanatom.com>
|
/backport to stable-2.24 |
|
/backport to stable-2.23 |
|
/backport to stable-2.22 |
|
The backport to stable-2.24 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable-2.24
git pull origin/stable-2.24
# Create the new backport branch
git checkout -b fix/foo-stable-2.24
# 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-stable-2.24More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
|
The backport to stable-2.23 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable-2.23
git pull origin/stable-2.23
# Create the new backport branch
git checkout -b fix/foo-stable-2.23
# 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-stable-2.23More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
|
The backport to stable-2.22 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable-2.22
git pull origin/stable-2.22
# Create the new backport branch
git checkout -b fix/foo-stable-2.22
# 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-stable-2.22More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
Didn't read very well before.