docs: give the README a picture of the timeline - #6
Merged
Merged
Conversation
The README explained a timeline you can play, and showed nothing. A tool whose whole point is watching a repository fill in should not have to be imagined from prose. The screenshot is the built-in demo at its final commit, so nothing in it came from anyone's repository: the working tree on the left, the commit and its four changed files in the middle, growth and file-type mix on the right, and the scrubbable timeline with its milestone marks along the bottom. It also happens to show the privacy claim being true rather than stated — the badge in the corner reads "0 GitHub requests", which is the whole reason the demo history is curated and shipped with the app. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
The README explained "a timeline you can play" and showed nothing. A tool whose
whole point is watching a repository fill in should not have to be imagined
from prose.
The screenshot is the built-in demo at its final commit, so nothing in it came
from anyone's repository:
+230 −2216 / 16It also shows the privacy claim being true rather than stated — the badge in
the corner reads
0 GitHub requests, which is the whole reason that demo historyis curated and ships with the app.
Verified:
npm run typecheckclean,npm testpassing.🤖 Generated with Claude Code