How pomber/git-history works
Project type and purpose
• This is an open-source, multi-interface “Git History” tool that lets you browse file history in any Git repo.
• It ships as:
• A Single Page Application (SPA) served on GitHistory.xyz (built with React + CRACO + Netlify)
• A command-line interface (CLI) for local repos (Node.js scripts under cli/)
• A VS Code extension (vscode-ext/)
File structure
• Top-level folders:
• src/ – the core library of UI components, animations, and “git-providers” modules
• public/ – static assets for the SPA
• cli/ – Node.js CLI commands and a local‐server entrypoint
• vscode-ext/ – the VS Code extension code and tests
• .storybook/ – story definitions for UI components
• Root files: craco.config.js (CRA override), netlify.toml (deploy config), travis.yml, package.json, readme.md
• Shared code lives in src/, especially src/git-providers/ which implements fetchers for GitHub/GitLab/Bitbucket/local.
Extract insights from the README
• The SPA fronts any Git host by rewriting URLs to github.githistory.xyz, then fetches commits via corresponding provider modules.
• The CLI and VS Code extension reuse the same provider logic to read local repositories.
• No database—data flows live from Git hosts or local repo to UI.