Screenshots for git-stats, and cross-links between the two plugins - #27
Merged
Merged
Conversation
git-stats had no picture, which for a plugin whose whole point is a colour-coded chip is the wrong thing to leave to the imagination. Two shots, both captured by driving a real OpenCode TUI through the pty harness and rendering the composed screen (the same rig that produced context-tree's screenshots): - sidebar-card.png — the card in the sidebar, next to the host's own Context and LSP sections, showing the working-tree figures and all four chip colours. - prs-dialog.png — the /prs picker, each row carrying the pull request's title. The chips are real pull requests in real states, read live from `gh`: cli/cli has draft, open, closed and merged open at once, and this repo's own PRs are all merged, so a capture here could only ever show one colour. Staging fake states would have made a prettier picture of something the plugin does not do. The figures in the shot are real too: the fixture repo has README +2, parser.ts +4/-2 and an untracked 2-line version.ts, which is exactly the `+8 -2 · 3 files` on screen. Both READMEs now point at each other, since the repo holds two plugins and someone landing on one should learn the other exists.
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.
git-statshad no picture, which for a plugin whose whole point is a colour-codedchip is the wrong thing to leave to the imagination.
Two shots, both captured by driving a real OpenCode TUI through the pty harness and
rendering the composed screen — the same rig that produced context-tree's existing
screenshots:
sidebar-card.png— the card in the sidebar beside the host's own Context andLSP sections, showing the working-tree figures and all four chip colours.
prs-dialog.png— the/prspicker, each row carrying the pull request's title.The chips are real
Read live from
gh, in real states.cli/clihappens to have draft, open, closed andmerged pull requests open at once; this repo's own 26 PRs are all merged, so a capture
here could only ever have shown one colour. Staging fake states would have produced a
prettier picture of something the plugin does not do.
The figures are real as well — the fixture repo has
README.md+2,parser.ts+4/-2,and an untracked 2-line
version.ts, which is exactly the+8 -2 · 3 fileson screen.Cross-links
Both READMEs now point at each other. The repo holds two plugins, and someone landing
on one should learn the other exists.
Screenshots are not added to either package's
filesarray, matching context-tree:npm resolves relative README image paths against
repository.directory, so they renderon the npm page without shipping in the tarball.