Repository navigation
Repair wp/6.3 branch Actions: Remove the broken flaky-test-to-GitHub-issues reporting job - #83700
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. |
932bb43 to
4c1e8a0
Compare
|
Size Change: 0 B Total Size: 1.46 MB ℹ️ View Unchanged
|
4c1e8a0 to
0d00c6d
Compare
0d00c6d to
3734c49
Compare
Part of #82930.
What?
Removes
end2end-test.yml'sreport-to-issuesjob, which files GitHub issues for detected flaky tests.Why?
The
report-to-issuesjob doesactions/checkout … ref: trunkbefore building and runningpackages/report-flaky-tests— it always executes live current trunk's copy of the action, never this frozen branch's own. Trunk has since retired thenpm run build:packagesscript this job's "Npm build" step calls, as part of migrating the action to run directly from TypeScript source via Node 24's native type-stripping and changing flaky-test reporting to a PR-comment-only model (WordPress/gutenberg#81218). I confirmed directly that current trunk'spackage.jsonno longer declares abuild:packagesscript at all.Removing the job only drops an automated notification; it has no effect on actual test-correctness signal, since it only ever reports on already-detected flaky tests after the fact and never gates a build.
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.