-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Revert "Pages: Trash view should default to table layout." #63481
Revert "Pages: Trash view should default to table layout." #63481
Conversation
This reverts commit 905b41d.
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: -21 B (0%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
Flaky tests detected in 8d2521c. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/9907592688
|
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, @jorgefilipecosta!
I think the original PR didn't include new perf tests, which are currently failing - #63170.
You might have to merge this with failing Perf job, because code still exists on trunk.
Co-authored-by: jorgefilipecosta <jorgefilipecosta@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
…#63481) Co-authored-by: jorgefilipecosta <jorgefilipecosta@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Reverts: #63138
Although the CI passed on the PR it caused the CI to fail on the trunk. Debugging it seems the CI error on the performance test is legitimate. I'm going to revert the PR and address the issue separately.