feat: use GitHub star history API for trends - #1105
Open
pastelsky wants to merge 10 commits into
Open
Conversation
pastelsky
force-pushed
the
codex/trends-data-sources-github-api-v3
branch
from
September 5, 2026 07:16
165d766 to
24a4eb8
Compare
pastelsky
commented
Sep 5, 2026
| } | ||
| } | ||
|
|
||
| export function parseGithubRepository( |
Owner
Author
There was a problem hiding this comment.
I thought we had an npm dep for this?
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
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
bundlephobiabranch/stargazers/historyendpoint for exact daily star actionsstargazers_countas a separate live snapshotData contract
The historical
starsseries is star actions, not cumulative star stock. Issue history and issue snapshots are intentionally absent from this feature until a reliable historical source is available.This supersedes the older cache protocol in #1089; do not merge both implementations. It is the backend/data-source PR to review before wiring the page in #1076.
Validation
yarn format:checkyarn typecheckyarn lint(existing warnings only)yarn builderrors-cachefixture failures remain in the local environmentThe GitHub endpoint documentation is at https://docs.github.com/en/rest/activity/starring?apiVersion=2026-03-10.