-
Notifications
You must be signed in to change notification settings - Fork 91
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
feat: update render markdown for tables #4390
Conversation
1 failed and 3 flaky tests on run #11873 ↗︎
Details:
cypress/e2e/attachments.spec.js • 1 failed test
share.spec.js • 2 flaky tests
api/SyncServiceProvider.spec.js • 1 flaky test
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
Cypress failure looks unrelated, but can you check the jest tests again @luka-nextcloud ? |
dc55e9c
to
e3bb72d
Compare
funny that the node check is passing without a compile. |
/backport e3bb72d to stable27 |
e3bb72d
to
1c63fab
Compare
/compile |
7a4fff2
to
c587f55
Compare
/compile |
Signed-off-by: Luka Trovic <luka@nextcloud.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
e109f0e
to
1c168c0
Compare
The backport to stable27 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable27
git pull origin stable27
# Create the new backport branch
git checkout -b fix/foo-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 abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27 More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
@luka-nextcloud Can you take care of the manual backport please? |
📝 Summary
🖼️ Screenshots
🚧 TODO
🏁 Checklist
npm run lint
/npm run stylelint
/composer run cs:check
)