Skip to content

docs: add test_step_outcome input to CI upload step documentation#10840

Merged
mergify[bot] merged 1 commit intomainfrom
devs/jd/worktree-test-exit-code/Ifb5f5f1b12e72b1b3059e37cc362f979fe8e6eba
Apr 3, 2026
Merged

docs: add test_step_outcome input to CI upload step documentation#10840
mergify[bot] merged 1 commit intomainfrom
devs/jd/worktree-test-exit-code/Ifb5f5f1b12e72b1b3059e37cc362f979fe8e6eba

Conversation

@jd
Copy link
Copy Markdown
Member

@jd jd commented Apr 3, 2026

Document the new test_step_outcome input added in Mergifyio/gha-mergify-ci#174.
This option lets users pass the test runner step's outcome so Mergify
can detect silent failures where the runner crashed but the JUnit
report appears clean.

Updated the shared upload step components and the quarantine setup
partial so the new input appears across all test framework pages.

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

Copilot AI review requested due to automatic review settings April 3, 2026 07:32
@mergify mergify bot had a problem deploying to Mergify Merge Protections April 3, 2026 07:32 Failure
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Apr 3, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 🤖 Continuous Integration

Wonderful, this rule succeeded.
  • 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/

🟢 👀 Review Requirements

Wonderful, this rule succeeded.
  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • author = mergify-ci-bot

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

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

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

🟢 🔎 Reviews

Wonderful, this rule succeeded.
  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

Wonderful, this rule succeeded.
  • body ~= (?ms:.{48,})

@jd jd marked this pull request as ready for review April 3, 2026 07:33
@mergify mergify bot requested a review from a team April 3, 2026 07:34
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates CI Insights documentation snippets to include the new test_step_outcome input for mergifyio/gha-mergify-ci, helping Mergify detect “silent failures” where the test runner crashes but the JUnit output looks clean.

Changes:

  • Add test_step_outcome to the standard and matrix upload-step YAML examples.
  • Document test_step_outcome in the upload-step “Key Points” list.
  • Extend the quarantine setup partial to recommend passing the test runner step outcome.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
src/content/docs/ci-insights/test-frameworks/_gha_mergify_ci_quarantine_setup.mdx Adds narrative guidance about passing test_step_outcome to detect silent failures.
src/components/MergifyCIUploadStepMatrix.astro Updates matrix upload-step YAML example to include test_step_outcome.
src/components/MergifyCIUploadStep.astro Updates upload-step YAML example and adds a “Key Points” entry documenting test_step_outcome.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Document the new `test_step_outcome` input added in Mergifyio/gha-mergify-ci#174.
This option lets users pass the test runner step's outcome so Mergify
can detect silent failures where the runner crashed but the JUnit
report appears clean.

Updated the shared upload step components and the quarantine setup
partial so the new input appears across all test framework pages.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Change-Id: Ifb5f5f1b12e72b1b3059e37cc362f979fe8e6eba
Claude-Session-Id: 312d910f-6126-4a7c-812a-91b4a2ad4e58
@jd jd force-pushed the devs/jd/worktree-test-exit-code/Ifb5f5f1b12e72b1b3059e37cc362f979fe8e6eba branch from 4dd7ab9 to 0ca3878 Compare April 3, 2026 09:23
@mergify mergify bot deployed to Mergify Merge Protections April 3, 2026 09:23 Active
@mergify mergify bot requested a review from a team April 3, 2026 09:27
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Apr 3, 2026

Merge Queue Status

This pull request spent 2 minutes 43 seconds in the queue, including 2 minutes 30 seconds running CI.

Required conditions to merge

mergify bot added a commit that referenced this pull request Apr 3, 2026
@mergify mergify bot added the queued label Apr 3, 2026
@mergify mergify bot merged commit 31c333c into main Apr 3, 2026
9 checks passed
@mergify mergify bot deleted the devs/jd/worktree-test-exit-code/Ifb5f5f1b12e72b1b3059e37cc362f979fe8e6eba branch April 3, 2026 09:34
@mergify mergify bot removed the queued label Apr 3, 2026
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.

4 participants