Fix typo in array_api docs#948
Merged
Merged
Conversation
Trivial change to verify the post-merge strict-status check flow from PR astropy#942 (a single ubuntu-py313-strict check run with a neutral conclusion is expected on this PR). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M5FNYqVHbKLbVSGJGftLrL
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #948 +/- ##
=======================================
Coverage 96.56% 96.56%
=======================================
Files 8 8
Lines 1571 1571
=======================================
Hits 1517 1517
Misses 54 54 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
mwcraig
added a commit
that referenced
this pull request
Jul 14, 2026
Post-merge verification of the workflow_run flow (test PR #948) showed no ubuntu-py313-strict check run was posted: with a pattern matching exactly one artifact, download-artifact extracts it directly into the destination directory instead of a per-artifact subdirectory, so the script's scan for strict-job-outcome-* directories found nothing and returned "nothing to report". Scan for the strict-outcome.json files themselves, supporting both the flat single-artifact layout and the per-artifact subdirectory layout that appears once the expected-failures matrix has more than one entry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M5FNYqVHbKLbVSGJGftLrL
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Trivial docs typo fix ("your encounter" -> "you encounter"), doubling as the post-merge verification for the strict-status reporting added in #942.
Expected on this PR, now that the workflow file is on the default branch and runs in the real
workflow_runflow:ubuntu-py313-strictcheck run appears (thepull_request-event gate working — not two);strict-job-outcome-ubuntu-py313-strictJSON artifact exists on the CI run.🤖 Generated with Claude Code
https://claude.ai/code/session_01M5FNYqVHbKLbVSGJGftLrL