Skip to content

merge queue: checking main (bc9c489) and #12417 together - #12502

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/a53d922f35
Closed

merge queue: checking main (bc9c489) and #12417 together#12502
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/a53d922f35

Conversation

@mergify

@mergify mergify Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (bc9c489) and #12417 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #12417.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: bc9c489ed30d43aa0806cb28be83b67ba3af4a38
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12417
    scopes: []
scopes: []
...

jd and others added 2 commits August 24, 2026 10:31
Every test framework recipe ends by sending the reader to the Test Insights
dashboard, and each one carried its own copy of that sentence. Ten of the copies
had drifted onto `https://dashboard.mergify.com/test-insights/jobs`, which is not
a page — Test Insights has Prevention, Detection and Mitigation — and an
eleventh named the dashboard with no link at all. #12490 has since corrected all
eleven in place, so the links work today; what it could not fix is why one stale
URL became ten broken links, which is that the sentence exists eleven times.

So the paragraph becomes `_review-in-test-insights.mdx`, included by the
recipes. The rendered text is byte-identical to what #12490 shipped; the next
time that link moves it is one edit rather than eleven, and a recipe cannot
quietly drift out of step with its siblings again. Shared partials are already
how these files handle the Buildkite quarantine setup and the upload steps.

Separately, two inline GitHub Actions examples were missing the
`continue-on-error: true` that the quarantine partial they include requires:
the Gradle example in the JUnit recipe and the `rake test` example in the
Minitest one. Without it a failing test step ends the job before the upload step
runs, so the run that most needs a report produces none — and in both files the
sibling example directly above already had the line, so this was drift rather
than a deliberate difference.

Part of MRGFY-8720

Change-Id: I482ec81d7710f37d83dcffdf65abc029b73437fc
@mergify
mergify Bot deployed to Mergify Merge Protections August 24, 2026 11:52 Active
@mergify mergify Bot closed this Aug 24, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/a53d922f35 branch August 24, 2026 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant