docs(test-insights): state that Detection reports on default-branch runs - #12260
Conversation
Merge Protections🔴 2 of 6 protections blocking · waiting on 👀 reviews
🔴 👀 Review RequirementsWaiting for
This rule is failing.
🔴 🔎 ReviewsWaiting for
This rule is failing.
Show 4 satisfied protections🟢 🤖 Continuous Integration
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
There was a problem hiding this comment.
🟡 Not ready to approve
Two small wording/style adjustments are needed in the newly added Detection section to match docs writing rules and remove ambiguity.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.
Pull request overview
Documents the scope of Test Insights Detection, clarifying that it reports only on default-branch CI runs (while pull request runs feed Prevention), and cross-links this behavior from the Test Insights overview page.
Changes:
- Add a new “Which runs Detection reports on” section to explain default-branch-only reporting and what to expect if CI has only run on pull requests.
- Clarify that the same scope applies to
mergify tests showand the Test Insights test search API. - Add a “Default branch scope” key concept with a deep link to the new Detection section.
File summaries
| File | Description |
|---|---|
| src/content/docs/test-insights/detection.mdx | Adds an explicit section describing Detection’s default-branch scope and related CLI/API scope. |
| src/content/docs/test-insights.mdx | Adds a key concept bullet that points readers to the new Detection scope explanation. |
Review details
Comments suppressed due to low confidence (1)
src/content/docs/test-insights/detection.mdx:23
- “Merge to the default branch” is a bit ambiguous (merge what?). Making it explicit helps readers understand they need a default-branch CI run (typically by merging a pull request).
A repository whose CI has only ever run on pull requests shows an empty
Detection page, even though uploads are working. Merge to the default branch
and the tests appear after that run completes.
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Low
We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.
Detection, `mergify tests show`, and the test search API surface only runs from the repository's default branch; pull request runs are stored but feed Prevention instead. A repository whose CI has only ever run on pull requests therefore sees an empty Detection page with working uploads. MRGFY-8295 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CCCgUbY1KiEvFJdvfc81a4 Change-Id: I408c578a358d2c2bf60387a6101af8c663eff888
dbc8116 to
d7168a0
Compare
Revision history
|
Detection,
mergify tests show, and the test search API surface only runsfrom the repository's default branch; pull request runs are stored but feed
Prevention instead. A repository whose CI has only ever run on pull requests
therefore sees an empty Detection page with working uploads.
MRGFY-8295
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01CCCgUbY1KiEvFJdvfc81a4