[desrosj]

What?

Removes the report-to-issues job (Report to GitHub) from .github/workflows/end2end-test.yml on wp/6.2.

Why?

report-to-issues checks out trunk (ref: trunk) rather than this branch, then runs npm run build:packages before invoking ./packages/report-flaky-tests — it always builds and runs live current trunk's copy of the action, never wp/6.2's own frozen copy.

Trunk has since removed the build:packages script from package.json as part of migrating report-flaky-tests to run directly from its TypeScript sources via Node 24's native type stripping (no build step: using: 'node24', main: 'src/index.ts' in trunk's packages/report-flaky-tests/action.yml). As a result, the job's npm run build:packages step fails with npm error Missing script: "build:packages" whenever it actually reaches that step — which it does whenever e2e-puppeteer/e2e-playwright produce a flaky-tests-report artifact for it to pick up.

This is directly confirmed as the currently-failing top-of-stack check, not just inferred from trunk's content: on PR #346 (the previous top of stack), the End-to-End Tests workflow's Report to GitHub job failed with exactly this error — run 34801278771, job 103934457687.

This is a structural failure, not a one-time regression: because the job always tracks a moving target (trunk) instead of this branch's own pinned copy, it will keep breaking as trunk's tooling around this action continues to evolve, independent of anything in wp/6.2 itself.

Retrofitting trunk's current version of report-flaky-tests was considered and rejected, matching the same decision already made on wp/6.3-wp/6.8 (where this same layer, disable-flaky-test-issue-reporting, already exists). Trunk's rewrite is also a product-policy change — flaky tests are now reported as PR comments only, and no longer filed as GitHub issues — which is out of scope for a frozen, security-maintenance-only branch.

Removing the job only drops an automated notification; no actual test-correctness signal depends on it. packages/report-flaky-tests is left in place on this branch, now unused by any workflow — removing the package itself is optional cleanup out of scope for this fix.

Testing

Diff mirrors the already-proven disable-flaky-test-issue-reporting layer used on wp/6.3-wp/6.8 (e.g. #134 on wp/6.3) — same job removed, same shape (this branch has no separate merge-artifacts/has-flaky-test-report gate to also touch). Will confirm this specific branch's Report to GitHub check goes from failing to not-present/passing via real CI on this PR before it's finalized.

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.

[github-actions]

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[desrosj]

Moved to WordPress#84220.