Repository navigation
Star history, taken from #163 on its own - #178
Merged
Merged
Conversation
Signed-off-by: Liangziyi <Danmushu@outlook.com> (cherry picked from commit 0185b1e)
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
2 participants
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.
Cherry-picks one commit from #163 — @Danmushu's
docs: add repository star history— with authorship kept. The other commit in that PR is a separate proposal and is not carried here.Two adjustments on top, in their own commit so they stay separable from the contribution:
Daily rather than weekly. A star curve that only moves once a week is flat for six days out of seven, and the shape of the growth is the whole point of the chart.
Pinned to a commit, not a tag. This is the first workflow in the repository with
contents: write—release.ymliscontents: readpluspackages: write. A tag can be repointed by the action's owner, so write access to the repository behind a movable reference means trusting code that can be swapped out.65836723is v3.34; the comment above it says so, for whoever upgrades. Running daily rather than weekly multiplies the exposure, which is the same reason.METRICS_TOKENdoes not exist yet, so the first run will fail and the README image stays broken until it succeeds — the SVG is committed by the workflow itself. The secret has to be added in repository settings;workflow_dispatchis there to trigger the first run by hand rather than waiting for the schedule.🤖 Generated with Claude Code