docs: static Docker badge (avoid shields.io upstream rate-limit)#291
Merged
Conversation
The live shields.io docker/pulls badge reads Docker Hub's metadata API, which is frequently throttled and renders as "rate limited by upstream service". Swap to a static badge that makes no API call and links to the Docker Hub repository. Image pulls go through the registry and are unaffected by this change.
smaramwbc
force-pushed
the
docs/static-docker-badge
branch
from
July 20, 2026 18:15
71b3f52 to
3935da4
Compare
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.
What
Replaces the live shields.io
docker/pullsbadge with a static Docker badge.Why
The pull-count badge reads Docker Hub's metadata API through shields.io's shared infrastructure, which Docker Hub throttles frequently. When that happens the badge renders as "rate limited by upstream service" — a broken-looking badge on a public README. The static badge makes no API call, so it always renders cleanly, while still linking to the Docker Hub repository.
Image pulls go through the registry and were never affected — this is purely a cosmetic badge fix.