Skip to content

docs(test-insights): state that Detection reports on default-branch runs - #12260

Open
JulianMaurin wants to merge 1 commit into
mainfrom
devs/JulianMaurin/MRGFY-8295/state-detection-reports-default-branch-runs--408c578a
Open

docs(test-insights): state that Detection reports on default-branch runs#12260
JulianMaurin wants to merge 1 commit into
mainfrom
devs/JulianMaurin/MRGFY-8295/state-detection-reports-default-branch-runs--408c578a

Conversation

@JulianMaurin

@JulianMaurin JulianMaurin commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

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

Copilot AI review requested due to automatic review settings July 29, 2026 14:52
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections July 29, 2026 14:52 Failure
@mergify

mergify Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🔴 2 of 6 protections blocking · waiting on 👀 reviews

Protection Waiting on
🔴 👀 Review Requirements 👀 reviews
🔴 🔎 Reviews 👀 reviews
🟢 🤖 Continuous Integration
🟢 Enforce conventional commit
🟢 📕 PR description
🟢 🚦 Auto-queue

🔴 👀 Review Requirements

Waiting for

  • #approved-reviews-by >= 2
This rule is failing.
  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • author = mergify-ci-bot

🔴 🔎 Reviews

Waiting for

  • #review-requested = 0
This rule is failing.
  • #review-requested = 0
  • #changes-requested-reviews-by = 0
  • #review-threads-unresolved = 0

Show 4 satisfied protections

🟢 🤖 Continuous Integration

  • all of:
    • check-success = build
    • check-success = lint
    • check-success = test
    • any of:
      • check-success = test-broken-links
      • label = ignore-broken-links
    • any of:
      • check-success=Cloudflare Pages
      • -head-repo-full-name~=^Mergifyio/

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

Comment thread src/content/docs/test-insights/detection.mdx Outdated
@JulianMaurin
JulianMaurin marked this pull request as ready for review July 29, 2026 14:53
@mergify
mergify Bot requested a review from a team July 29, 2026 14:54

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 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 show and 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.

Comment thread src/content/docs/test-insights/detection.mdx Outdated
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
@JulianMaurin
JulianMaurin force-pushed the devs/JulianMaurin/MRGFY-8295/state-detection-reports-default-branch-runs--408c578a branch from dbc8116 to d7168a0 Compare July 29, 2026 14:58
@JulianMaurin

Copy link
Copy Markdown
Contributor Author

Revision history

# Type Changes Reason Date
1 initial dbc8116 2026-07-29 14:58 UTC
2 content dbc8116 → d7168a0 (raw) Applied review: dropped the default-branch caution (obvious) and replaced 'health, confidence, and impact' with 'the metrics shown here'. 2026-07-29 14:58 UTC

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections July 29, 2026 14:58 Failure
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.

2 participants