Repository navigation
docs: pin CI badges to main branch - #237
Merged
Merged
Conversation
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.
Summary
Both CI badges in README.md pointed at .../workflows/lint.yml/badge.svg and .../workflows/test.yml/badge.svg with no branch qualifier. GitHub's workflow badges without a �ranch query param reflect the most recent run across any branch, not specifically main. This made the badges flicker to red whenever a run on a feature branch or PR failed, even if main itself was green.
Change
Added ?branch=main to both badge URLs so they always reflect the status of main's latest run.
Testing
Documentation-only change, no code affected. Verified the badge URL format against GitHub's shields documentation convention (/badge.svg?branch=).