ci: report README badge status from dev - #9512
Merged
Merged
Conversation
The Unit Tests badge showed the last run of unit-tests.yml regardless of branch, which meant a red badge from an unrelated PR branch. Pin both workflow badges to dev and run unit tests on pushes to dev so the badge has a dev-branch result to point at. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Problem
The Unit Tests badge in the README was red, but not because dev is broken.
unit-tests.ymlonly triggers onpull_requestandpush: [main], so it has never run on dev. A badge with no?branch=falls back to the workflow's latest run, which happened to be a failing PR branch (pjwerneck/restrict-allowed-audit, missingjax). Dev's unit tests pass locally — 218 passed forjust test-unit-restrict.Change
unit-tests.yml:branches: [main]→branches: [main, dev], so merges to dev produce a dev-branch run for the badge to point at.README.md: both workflow badges get?branch=dev, and the links go to?query=branch%3Adevso clicking through shows only dev runs.PR runs are unaffected — the
pull_request:trigger is untouched, andpushonly fires when something lands on dev.Notes
test_do_cache_aware_sync_gdrive,test_pagination_and_early_termination,test_google_drive_connection_load_state) — that is a genuine dev failure, not badge noise.🤖 Generated with Claude Code