Idea
Explore commits as squares in the GitHub Explorer.
Why
Commits may be visually rich enough to deserve their own grid:
- recency / chronology;
- author/committer;
- signature/verification state;
- PR association;
- CI outcome near the commit;
- revert/merge/bot/generated patterns;
- size or touched-area hints.
The goal is not to commit to a product feature yet. First, prototype what a commit grid looks like and whether the attributes make useful visual states.
Data/cost concern
This is likely expensive if the app continuously queries GitHub directly from the browser. It probably pushes us toward a more robust long-term caching strategy rather than relying only on browser storage and live GitHub API calls.
Related nearby issue: #1 covers explicit incomplete/rate-limited data states. Commit squares may need the next step beyond that: durable or precomputed GitHub data snapshots.
Idea
Explore commits as squares in the GitHub Explorer.
Why
Commits may be visually rich enough to deserve their own grid:
The goal is not to commit to a product feature yet. First, prototype what a commit grid looks like and whether the attributes make useful visual states.
Data/cost concern
This is likely expensive if the app continuously queries GitHub directly from the browser. It probably pushes us toward a more robust long-term caching strategy rather than relying only on browser storage and live GitHub API calls.
Related nearby issue: #1 covers explicit incomplete/rate-limited data states. Commit squares may need the next step beyond that: durable or precomputed GitHub data snapshots.