nirmalscaria/le-git-graph

★ 5,878JavaScriptAudience · developerComplexity · 1/5Setup · easy

Mindmap

mindmap
  root((le-git-graph))
    What it does
      Commit graph view
      Branch visualization
      GitHub enhancement
    Browser support
      Chrome and Edge
      Firefox
      Brave and Opera
    Features
      Branch filtering
      Commit detail hover
      Load more commits
      Private repo support
    Setup
      OAuth login
      Personal Access Token
      One-time install

mindmap root((le-git-graph)) What it does Commit graph view Branch visualization GitHub enhancement Browser support Chrome and Edge Firefox Brave and Opera Features Branch filtering Commit detail hover Load more commits Private repo support Setup OAuth login Personal Access Token One-time install

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Understand a complex project's branching history at a glance by seeing how features were merged into main.

USE CASE 2

Track when and where a bug was introduced by browsing the commit graph timeline directly on GitHub.

USE CASE 3

Filter commits by branch to focus on one feature's history without leaving the GitHub interface.

Tech stack

JavaScript

Getting it running

Difficulty · easy Time to first run · 5min

Private organization repos require creating and manually entering a GitHub Personal Access Token into the extension settings.

In plain English

Le Git Graph is a browser extension that adds a visual commit history graph to any GitHub repository page. GitHub's default interface shows commits as a plain list, but a graph makes it much easier to see how branches split apart and merge back together over time. This extension adds that graph as a new tab called "Commits" directly inside the GitHub website. It works in Chrome, Edge, Brave, Opera, Vivaldi, and Firefox. After installing it from the relevant browser extension store and visiting any GitHub repository, the Commits tab appears automatically. Clicking it prompts a one-time login with a GitHub account so the extension can fetch the commit data. The extension asks for read-and-write permission to repositories, which the README acknowledges looks broader than necessary. The reason is that GitHub's OAuth system does not offer a read-only option for repositories, so the extension must request the broader permission even though it only ever reads data. The source code is available for anyone who wants to verify this. For private repositories owned by an organization, extra steps are needed. Organizations restrict third-party access by default, so users must create a Personal Access Token on GitHub and enter it into the extension manually. The README walks through this process step by step. Features include hovering on individual commits to see details, filtering commits by branch, loading more commits on demand, and choosing whether to include private repositories or limit access to public ones only.

Copy-paste prompts

Prompt 1

I have Le Git Graph installed and I'm looking at a repo with 50 branches. How do I filter the graph to show only commits from a specific branch?

Prompt 2

Walk me through setting up Le Git Graph for a private GitHub organization repo using a Personal Access Token, include every step from creating the token to entering it in the extension.

Prompt 3

I want to build a similar browser extension that fetches GitHub commit data and renders a graph. What GitHub API endpoints would I use and how would I structure the Chrome extension manifest?

Open on GitHub → Explain another repo

← nirmalscaria on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.