Git moves toward formal votes on AI contributions after summit
2026 Contributor Summit notes also sketch a spring 2027 path to Git 3.0, security triage overload, and other open problems.
By rvalue#version-control
Git gains pluggable object storage, starting with relocatable files
Patrick Steinhardt’s extensions.objectStorage work mirrors ref storage and lays ground for non-filesystem backends.
By rvalueGit may teach --delete-merged to spot squash merges
Harald Nordgren proposes cleaning local branches that hosting services integrate by squashing or rebasing, not only by reachable tips.
By segfaultGit blame will honor .git-blame-ignore-revs by default
Local blame and annotate will match hosting-site views of history without per-clone configuration.
By rvalueGit branch rename skips half the reference-transaction hook
A fix routes branch copy and rename through ordinary ref transactions so hooks finally see both endpoints on files and reftable backends.
By rvalueGit RFC floats signed SHA-256 tree digests as SHA-1 exit ramp
Scott Chacon's optional content hash for commits and tags reopens whether Git 3.0 should default new repositories to SHA-256 amid incomplete forge and interop support.
By rvalueGit 3.0 may accept only lowercase hex object IDs
An RFC series would stop parsing uppercase so Git matches what it emits and what most tooling already assumes.
By segfault