BRENNEN

Industries / Technology / Software and SaaS / Developer tools

Version control and review

Keeping every past version of a project's code, merging the work of many people, and checking each change before it goes in.

7

Milestones achieved, from 1972 to 2020.

2

To watch for: announced, not yet confirmed outside.

2

Open deliverables. Nobody has shipped them.

The road

AchievedWatch forOpen

Achieved

  1. 1972

    Changes stored as deltas

    Marc Rochkind at Bell Labs built the Source Code Control System (SCCS), first as a prototype on an IBM 370 computer begun in 1972. Instead of a full copy of every version of a program, it kept the original and each later change, a "delta", and rebuilt any version by applying the deltas in order. It also stamped each version with its number and date, recorded who changed what, and controlled who was allowed to make changes. By Rochkind's account one person coded, debugged and tested the first release in under three months, and by 1975 a rewrite for Unix on a PDP-11 was used by "almost all software projects" at his Bell Labs site.

    ccy05327.github.io

    Credit

    Marc J. Rochkind, Bell Laboratories

  2. 1986

    Commit without locking

    SCCS and RCS, the Revision Control System that Walter Tichy built at Purdue University in the early 1980s, let one person at a time lock a file to change it. Dick Grune of the Vrije Universiteit Amsterdam wrote CVS, the Concurrent Versions System, so that he and two students with different working hours could change the same compiler at once. Each person edits a private copy; CVS merges in others' newer changes and flags the rare clashes for a person to fix. CVS stored its files in RCS's format. Grune described it in a 1986 report, and CVS won the USENIX STUG Award in 2003.

    dickgrune.comgnu.org

    Credit

    Dick Grune, with his students Erik Baalbergen and Maarten Waage; Walter F. Tichy for RCS

  3. 2008

    Changes offered by request

    GitHub, a website that hosts projects kept in Git, added pull requests on 23 February 2008, during its test period, and opened to the public on 10 April 2008. A pull request asks a project's owners to take in a set of changes, and gives everyone a place to discuss and review them before they are merged. By GitHub's count, more than 180 million developers worked on the site in 2025 and merged an average of 43.2 million pull requests a month.

    github.bloggithub.bloggithub.blog

    Credit

    GitHub

  4. 2013

    Reviews find fewer bugs

    In code review, a colleague reads a change before it is merged. Alberto Bacchelli and Christian Bird observed, interviewed and surveyed developers and managers at Microsoft and sorted hundreds of review comments by hand. Finding defects was the main reason people gave for reviewing, but reviews found fewer defects than expected. Their main yield was knowledge passed between people, awareness of what the team was doing, and better solutions. Understanding the change was the hardest part, and the tools did little to help.

    LessonReview works mostly as a way to share knowledge, so review tools should help people understand a change, not only spot bugs.

    microsoft.com

    Credit

    Alberto Bacchelli and Christian Bird; Microsoft Research, May 2013

  5. 2016

    One repository for Google

    In 2016 Rachel Potvin and Josh Levenberg described in Communications of the ACM how Google keeps nearly all its code in one repository, a monorepo, instead of one per project. By Google's account in its 2020 book Software Engineering at Google, about 50,000 engineers share it. Piper, the version control system Google built for it, holds more than 80 TB and takes 60,000 to 70,000 commits each working day. An OWNERS file in each directory names who may approve changes there, and a "One-Version" rule allows only one version of each library.

    research.googleabseil.io

    Credit

    Rachel Potvin and Josh Levenberg, Google

  6. 2017

    Windows moves to Git

    Microsoft moved the code of Windows, about 3.5 million files that make a Git repository of about 300 GB, from its in-house Source Depot, where it was split across more than 40 depots, into one Git repository. About 2,000 engineers switched over one weekend in March 2017, and by May about 3,500 of 4,000 Windows engineers were on Git, making 8,421 pushes a day on average. To make it work, Microsoft built GVFS (Git Virtual File System), which downloads only the files an engineer opens; with unmodified Git, it said, many commands would have taken 30 minutes to hours. Git itself took up the approach: Git 2.38, released in October 2022, includes Scalar, Microsoft's tool that turns on Git's features for very large repositories.

    devblogs.microsoft.comgithub.blog

    Credit

    Brian Harry's team at Microsoft; the Git project

  7. 2020

    Mercurial repositories switched off

    Bitbucket, Atlassian's code host, began in 2008 supporting only Mercurial, a version control system that, like Git, gives every developer a full copy. In 2020 it dropped Mercurial, citing a Stack Overflow survey in which almost 90% of developers used Git and about 3% Mercurial, and fewer than 1% of new Bitbucket users choosing it. New Mercurial repositories stopped on 1 February 2020, existing ones became read-only on 1 July, and all were disabled by 26 August 2020. Software Heritage, the largest public archive of source code, and the Mercurial specialists Octobus rescued about 250,000 endangered public Mercurial repositories.

    LessonCode kept only on one host, in a format the host can drop, needs a copy somewhere else before the deadline.

    atlassian.comsoftwareheritage.org

    Credit

    Atlassian; Software Heritage and Octobus for the rescue

Watch for

  1. SHA-256 by default

    Git names every file and commit by a hash, a fingerprint computed from its contents. Its default hash, SHA-1, has known practical attacks, so Git 3.0 will make SHA-256 the default for new repositories, make reftable (a newer format for storing branch and tag names) the default, and require the Rust programming language to build Git. At the Git Contributor Summit, held during Git Merge 2026 in Lisbon, Git's developers set a schedule: after Git 2.56 in September 2026, the version number jumps to 2.98 in December 2026 as a signal that a big change is coming, then 2.99 and 3.0 ship together in spring 2027. GitLab says it has supported SHA-256 repositories for a year; GitHub announced a private beta, with general availability to follow "in a few months".

    Achieved whenGit 3.0 ships with SHA-256 as its default, and a new SHA-256 repository can be pushed to and cloned from GitHub, GitLab and Codeberg without errors.

    about.gitlab.comgit-scm.com

    Claimed by

    Git's contributors, as reported by GitLab, September 2026

  2. Pull requests turned off

    Zed Industries' DeltaDB is a version control system that records every edit, by a person or an AI agent, beside the conversation that produced it, so teammates can review work while it is being written instead of in a pull request after a commit. Zed says Delta, the review tool built on it, works alongside Git, and that it has switched off pull requests on Delta's own repository and builds Delta entirely inside Delta.

    Achieved whenteams outside Zed run real projects on Delta without pull requests for several months, and an outside party compares their review times and bugs found after release with their earlier work on pull requests.

    zed.devzed.dev

    Claimed by

    Zed Industries, June and September 2026

Open

  1. 01

    SHA-256 support, tested

    A public table, rerun every month until Git 3.0 ships, that tests by script whether each code host, Git library and tool works with a SHA-256 repository. Eight operations: create, push, clone, fetch, open a pull or merge request, run a CI job (an automatic build and test), show line history in an editor, and mirror to a second host. Hosts: GitHub, GitLab, Bitbucket, Azure DevOps, Codeberg and a self-run Gitea. Libraries that programs use to read Git data: libgit2, JGit, go-git, gitoxide and Dulwich. Tools: GitHub Actions' checkout step, GitLab CI, Jenkins' Git plugin, and the Git views in VS Code and a JetBrains IDE.

    The brief
    Credit · unclaimed
  2. 02

    Small hosts, archived or not

    A count of how much public code on smaller code hosts is safely copied in the Software Heritage archive. List public instances of Forgejo, Gitea and GitLab run by universities, communities and companies; sample repositories from each through its own interface for programs; ask Software Heritage's public interface whether each repository is archived and when it was last visited; and publish the share archived for each instance. Send the list of missed instances to Software Heritage.

    The brief
    Credit · unclaimed

Open 01 · the brief

SHA-256 support, tested

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A public table, rerun every month until Git 3.0 ships, that tests by script whether each code host, Git library and tool works with a SHA-256 repository. Eight operations: create, push, clone, fetch, open a pull or merge request, run a CI job (an automatic build and test), show line history in an editor, and mirror to a second host. Hosts: GitHub, GitLab, Bitbucket, Azure DevOps, Codeberg and a self-run Gitea. Libraries that programs use to read Git data: libgit2, JGit, go-git, gitoxide and Dulwich. Tools: GitHub Actions' checkout step, GitLab CI, Jenkins' Git plugin, and the Git views in VS Code and a JetBrains IDE.

Why it is still open

The best public table found, published by DevToolLab on 2 October 2026, covers three hosts, GitHub, GitLab and Forgejo, from their documents and user reports. It did not test GitHub, and it covers no libraries or tools. GitHub's own support was still in private beta in September 2026.

devtoollab.comabout.gitlab.com

Built with what exists

Git 2.56 or later (git init --object-format=sha256 makes a SHA-256 repository); free accounts on each host; a shell or Python test harness; a scheduled CI job to rerun it each month.

  1. First step

    Make one SHA-256 repository and try to push it to GitHub, GitLab and Codeberg, recording each error message word for word.

  2. Done looks like

    At least 20 hosts, libraries and tools, each with a pass or fail on all 8 operations and the exact error for each failure, rerun monthly with the scripts published so anyone can repeat them. Every failure is filed as a bug report and linked from the table.

Open 02 · the brief

Small hosts, archived or not

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A count of how much public code on smaller code hosts is safely copied in the Software Heritage archive. List public instances of Forgejo, Gitea and GitLab run by universities, communities and companies; sample repositories from each through its own interface for programs; ask Software Heritage's public interface whether each repository is archived and when it was last visited; and publish the share archived for each instance. Send the list of missed instances to Software Heritage.

Why it is still open

Software Heritage says its main way of collecting code is "large-scale automated crawling of major software development forges". The Bitbucket shutdown of 2020 showed how quickly code on one host can disappear. A search found no published audit of how much code on smaller public hosts the archive holds.

arxiv.orgsoftwareheritage.org

Built with what exists

Software Heritage's public REST interface, which answers whether a repository's address is in the archive (for example https://archive.softwareheritage.org/api/1/origin/https://github.com/git/git/get/) and lists its visits; the shared Forgejo and Gitea interface and GitLab's, used within each host's rate limits; Python.

  1. First step

    Pick five public Forgejo instances, sample 20 repositories from each, and check all 100 against Software Heritage's interface.

  2. Done looks like

    100 public instances, 50 repositories sampled from each, 5,000 checks in all, with the share archived and the median days since the last archive visit for each instance. Data and scripts are published, and the missed instances are reported to Software Heritage, with a count a year later of how many it added.