The Unmerged: every repo is a record of what didn't get built

Description and use

The Unmerged scans public repositories to surface abandoned pull requests, unmerged branches, reverted commits, and delete-only commits, then uses the open‑weight SmolLM2‑360M‑Instruct model to generate concise intent statements, all running locally in the browser.

Problem

Public repositories contain abandoned work—closed pull requests, unmerged branches, reverted commits, and delete-only commits—that is rarely examined, leaving valuable insights hidden.

Outcome

The tool reveals 18 abandoned artifacts in facebook/react, including multiple long-lived branches, and produces concise intent statements for each, demonstrating the value of inspecting the unmerged half of repository history.

Workflow

• 1. User enters a public repo name (owner/name).
• 2. The tool makes four GitHub REST API calls: repo metadata, last 100 commits, last 100 closed PRs, and branch list.
• 3. It classifies artifacts into four categories: Unmerged PRs, Forsaken branches, Revenants (reverted commits), and Erased (delete-only commits).
• 4. For each artifact, the open-weight model (SmolLM2‑360M‑Instruct) generates a concise intent statement.
• 5. Results are displayed in the browser without any server or API key.
• 6. Optional GitHub token can be supplied to increase API rate limits.

Evidence

The Unmerged reads a public repository's history, finds the work that was abandoned in it, and has an open-weight model — running inside your browser tab — say what each piece of that work was trying to do.

Source

Three static files and a licence. No build step, no dependencies, no backend.

Source

The model is SmolLM2-360M-Instruct — Apache-2.0 weights, openly published training data — running through Transformers.js on WebGPU where the browser offers it and WASM where it doesn't.

Source

Reading is four calls to the GitHub REST API: repository metadata, the last hundred commits, the last hundred closed pull requests, the branch list.

Source

Point it at facebook/react and it finds eighteen of them, including branches named 0.3-stable through 0.9-stable — each still pointing at a commit, each still waiting.

Source