Repository navigation
Repair wp/6.5 branch Actions: Remove the broken flaky-test issue reporting job - #82996
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
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. |
e78f118 to
7d15f49
Compare
|
Size Change: 0 B Total Size: 1.72 MB ℹ️ View Unchanged
|
7d15f49 to
19e0b42
Compare
19e0b42 to
6b3a8fc
Compare
27d56bc to
e472585
Compare
e472585 to
927029a
Compare
927029a to
b8adf28
Compare
b8adf28 to
687b5bc
Compare
wp/6.5 branch Actions: Remove the broken flaky-test-to-GitHub-issues reporting jobwp/6.5 branch Actions: Remove the broken flaky-test issue reporting job
andrewserong
left a comment
There was a problem hiding this comment.
Looks like a clean removal to me, and removing is the right approach IMO for older releases 👍
Part of #82928.
What?
Removes the
report-to-issuesjob (display name "Report to GitHub") fromend2end-test.ymlonwp/6.5. Unlikewp/6.8(#82889), this branch has nomerge-artifactsjob orhas-flaky-test-reportoutput feeding it —e2e-puppeteerande2e-playwrighteach upload aflaky-tests-reportartifact directly, andreport-to-issuesdepends on both directly (needs: [e2e-puppeteer, e2e-playwright],if: always()).Why?
report-to-issueschecks out livetrunkbefore runningpackages/report-flaky-tests, rather than this frozen branch's own copy. Trunk retired thebuild:packagesnpm script this job calls, as part of migrating the action to run directly from TypeScript source via Node 24's native type-stripping (WordPress/gutenberg#81218) — the step will fail withnpm error Missing script: "build:packages"the next time it actually runs (it's gated onsteps.download_artifact.outcome == 'success', so it only runs when a test flakes).Retrofitting the job to match trunk's current implementation was rejected: trunk's replacement is also a real product-policy change (flaky tests become PR-comments-only, no more GitHub issues filed), out of scope for a frozen, security-maintenance-only branch. Removing the job only drops an automated notification; no test-correctness signal depends on it.
packages/report-flaky-testsis left in place, unused by any workflow on this branch — removing the package itself is optional cleanup out of scope here.Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.