Skip to content

docs: fix broken star history chart - #93

Open
OctoBored wants to merge 1 commit into
wanxingai:mainfrom
OctoBored:fix/star-history-chart
Open

docs: fix broken star history chart#93
OctoBored wants to merge 1 commit into
wanxingai:mainfrom
OctoBored:fix/star-history-chart

Conversation

@OctoBored

Copy link
Copy Markdown

The star history chart in our README is currently broken because its data source relies on the GitHub stargazer API, which now enforces strict rate limits that prevent the chart from loading. This change points the chart to a working alternative service so contributors and users can see the project history again. The same fix is applied to the Chinese translation of the README.

The star history chart in the README is currently broken because it relies on the GitHub stargazer API, which now enforces strict rate limits. Update the chart to point to a working service so the project history renders correctly again. Applies the same change to the localized Chinese README.

@wxai-space wxai-space left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for addressing the broken chart concern. The GitHub stargazer API restriction is a real upstream issue, but this patch silently replaces the official Star History service with a community-operated fork. At review time, both the existing and proposed SVG endpoints return HTTP 200, so availability alone does not establish that this replacement should become a repository dependency.

Please update the PR before merge:

  1. Clearly identify star-history.dera.page as the SimRepo/community Star History fork and link its source repository.
  2. Explain the data source, maintainer/ownership boundary, and whether the README image request requires or transmits credentials.
  3. Keep the README destination link pointed at an auditable project/source page rather than silently replacing the official project with a third-party service homepage.
  4. Explain why using this external service is preferable to removing the dynamic chart or using a repository-owned static image.

We will not approve the external-contributor workflow until the dependency and trust decision is resolved.

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.

2 participants