-
Notifications
You must be signed in to change notification settings - Fork 94
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: remove duplicated save key action #4495
Conversation
1 failed and 2 flaky tests on run #10994 βοΈ
Details:
Β cypress/e2e/sync.spec.js β’ 1 failed test
Β nodes/Mentions.spec.js β’ 1 flaky test
Β files.spec.js β’ 1 flaky test
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
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.
Thanks, works like expected π
@luka-nextcloud could you take care of backporting this to stable27, stable26 and stable25?
Signed-off-by: Luka Trovic <[email protected]>
4792589
to
e187a7c
Compare
/compile |
Signed-off-by: nextcloud-command <[email protected]>
/backport e187a7c to stable27 |
/backport e187a7c to stable26 |
/backport e187a7c to stable25 |
The backport to stable25 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable25
git pull origin stable25
# Create the new backport branch
git checkout -b fix/foo-stable25
# 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-stable25 More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
π Summary
πΌοΈ Screenshots
π§ TODO
π Checklist
npm run lint
/npm run stylelint
/composer run cs:check
)