Graph Tab for GitHub bởi Andrey Dodonov

Adds new tab to GitHub, "Graph", showing Git Graph for the current repository.
Does NOT require any permissions for your GitHub profile or browser.

Works for public repos even without logging in to GitHub.

Open any repository, click the new "Graph" tab, and see branches, merges, and history laid out like git log --graph.

PROS IN DETAILS

• Zero setup. No token to paste, no OAuth to approve, no options page. Install and click the tab.

• Zero permissions. The extension requests no GitHub or Chrome permissions at all. It runs only on github.com and talks only to github.com, riding the session you're already logged in with. Private and org repos work exactly like public ones — if you can view the repo, you can see its graph.

• No data collection. There is no backend, no analytics, no external requests of any kind. Your code and your browsing never leave github.com.

• Trying to feel native. The tab is styled with GitHub's own CSS variables, so light and dark themes both look right. The view lives at a #graph URL, so refresh, back/forward, and shared links all behave.

• Small and direct. Vanilla JS, no frameworks, no build step, no minification — you can read every line of what you install.

• Open source. You can verify all the points above at
https://github.com/AndreyDodonov-EH/graph-tab

CONS IN LIMITATIONS, A.K.A. HONEST LIMITATIONS

• It relies on GitHub's undocumented network-graph endpoints (the ones GitHub's own Insights → Network page uses). If GitHub changes them, the extension may break until it's updated. There is no official API being used, because the official API can't do this without a token.

• GitHub's graph data can lag recent pushes by minutes to hours. The extension compensates by re-reading branch heads live: automatic and fast for public repos; for private repos it's an opt-in checkbox ("fetch fresh commits") because it costs one request per missing commit.

• History loads in windows, newest first. For very deep histories you'll click "Load older commits" repeatedly rather than jumping straight to the initial commit.

• Early release. It's tested and used daily, but expect rough edges — bug reports are welcome at
https://github.com/AndreyDodonov-EH/graph-tab/issues

It can't be done perfectly, since the whole goal is no auth, which comes at a cost of using undocumented endpoints, unless GitHub itself ever does something similar.