fix: restore the broken star history chart in the README - #89
Open
FaintFlower wants to merge 1 commit into
Open
Conversation
The star history chart in the README was broken: GitHub's stargazer API restrictions took down the upstream renderer, so the badge and its link no longer load. Point both the image and the wrapping link at a maintained mirror of the same chart that needs no API token, restoring the graph in the readme.
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.
The star history chart embedded in the README stopped rendering because the upstream service broke under GitHub's stargazer API restrictions, and its mirror uses the same domain for the API and the frontend. This updates the chart image and its link to a working mirror of the same graph so the readme displays the star history again. The mirror handles requests on the shared domain and needs no API token.