Skip to content

docs(readme): give each CI badge a branch-specific label - #193

Merged
pacphi merged 1 commit into
mainfrom
followup/fix-readme-badge-labels
Apr 26, 2026
Merged

pacphi merged 1 commit into
mainfrom
followup/fix-readme-badge-labels

Conversation

@pacphi

@pacphi pacphi commented Apr 26, 2026

Copy link
Copy Markdown
Owner

Summary

GitHub's native workflow badge endpoint takes the label from the workflow's `name:` field. All three branches' CI shims live in `ci.yml`, so every badge previously rendered as just "CI" with no way to tell v2 from v3 from v4.

Switched the three CI badges to shields.io's `actions/workflow/status` endpoint with an explicit `label=vX: CI` per branch. Link targets are unchanged.

Test plan

  • After merge, badges show "v2: CI / passing", "v3: CI / passing", "v4: CI / passing" (or failing) on the rendered README

🤖 Generated with Claude Code

GitHub's native workflow badge endpoint pulls the label from the
workflow's name: field. All three branches share ci.yml and render
identically as "CI", making it impossible to tell which branch a
badge represents.

Switch the three CI badges to shields.io's actions/workflow/status
endpoint and pass an explicit label=vX: CI per branch. The badge link
target is unchanged (still goes to the per-branch run history).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@pacphi
pacphi merged commit 79253e8 into main Apr 26, 2026
5 checks passed
@pacphi
pacphi deleted the followup/fix-readme-badge-labels branch April 26, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant