Gerrit User Summit 2026: Code review in the agentic era

In two weeks, the Gerrit community is heading back to where it all started.

On 9–10 November, Gerrit User Summit 2026 will take place at Google’s campus in Sunnyvale, California. Gerrit Code Review was born at Google in Silicon Valley, and the last summit Google hosted was organised by Gerrit’s and JGit’s founder, Shawn Pearce, ten years ago.

The summit is free, open to anyone who registers, and hosted by Google in cooperation with GerritForge and the Gerrit community. Two days of talks, demos and conversations with the people who build, run and depend on Gerrit at scale, plus a morning of jj talks and a three-day hackathon hosted and organised by NVIDIA straight afterwards.

The full agenda is now live. Here’s what’s on each day, and why this year’s programme is one not to be missed.

Code review in the age of agents

AI coding agents are writing more code than ever. Someone – or something – still has to review it, validate it and ship it safely.

That question runs right through this year’s programme. Speakers from Google, NVIDIA, ACME Gating, GitLab and GerritForge are tackling how code review holds up when agents join the team: keeping agentic coding safe, managing load when automated traffic spikes, and scaling Git storage for workloads nobody planned for five years ago.

Alongside that, the summit keeps what the community values most: deep technical sessions from the maintainers themselves, real-world stories from teams running Gerrit in production, and plenty of time to talk to the people behind the code.

Day One – Nov 9: Core Architecture, Scaling, and Agentic Workflows

Day one is about Gerrit itself: what’s new, what’s next, and how the teams running it at scale keep it fast.

Luca Milanesio (GerritForge) opens with the latest highlights from the release, and later lays out how Gerrit and JGit are being rebuilt for AI-era storage. Monty Taylor – who helped launch OpenStack and designed the workflows that became Zuul and OpenDev – makes the case for keeping agentic coding safe with the human collaboration tools we already trust. In the afternoon, Hudson River Trading, NVIDIA and GitLab share what they’ve learned running Git and Gerrit under serious load.

  • 9:30 AM: What’s new in Gerrit v3.15 – Luca Milanesio, GerritForge
  • 10:15 AM: Improvements to the replication plugin – Kaushik Lingarkar, NVIDIA
  • 11:05 AM: Gerrit, Zuul and OpenClaw: safe agentic coding via human collaboration tools – Monty Taylor, Zuul and OpenDev
  • 11:50 AM: Multipack index support in JGit – Ivan Frade, Google
  • 1:20 PM: Scaling Gerrit and JGit for the AI era: a pluggable object backend with Cassandra – Luca Milanesio, GerritForge
  • 2:05 PM: From cgit to Gitiles: building repository search for everyone – Devansh Varshney, LibreOffice
  • 2:20 PM: HRT’s Gerrit improvements – Kamen Yotov, Hudson River Trading
  • 3:05 PM: Do I have to approve this again? Sticky Owners in Gerrit – Antonio Barone, GerritForge
  • 4:00 PM: Task quotas in the age of AI – Adithya Chakilam, NVIDIA
  • 4:30 PM: Large object promisors: handling large files natively in Git – Christian Couder, GitLab
  • 5:00 PM: Pimp your Gerrit: upgrade, tune, measure, repeat – Fabio Ponciroli, GerritForge
  • 5:30 PM: Social and networking

Doors open at 8:45 AM for registration.

Day Two – Nov 10: jj mini-summit and the future of Git scalability

Day two opens with a morning of jj and version control talks, co-hosted with the Jujutsu community, before turning to scaling for the AI era.

Google engineers share how they’re bringing jj into everyday workflows, from a VS Code extension to an open-source commit cloud. Daniele Sassoli and Emily Shaffer show what it takes to add native jj support to Gerrit. After lunch, Zuul creator Jim Blair joins Luca Milanesio on AI development at scale, and Shane McIntosh from the University of Waterloo presents research on keeping Git fast under AI workloads.

The summit closes with an open Q&A with the maintainers – your chance to ask the people steering Gerrit’s future anything you like.

  • 9:45 AM: jj VS Code extension at Google – Kevin Liao, Google
  • 10:15 AM: Version control and code formatting – Danny Hooper, Google
  • 10:45 AM: Where does your metadata live? – Patrick Hiesel, Google
  • 11:30 AM: Bridging the gap: adding native jj support to a Git-based SCM – Daniele Sassoli, GerritForge, and Emily Shaffer, Google
  • 12:00 PM: cloud-jj: an open-source commit cloud for jj – Daniel Sperry, Google
  • 1:30 PM: AI development at scale with Gerrit and Zuul – Jim Blair, Acme Gating, and Luca Milanesio, GerritForge
  • 2:15 PM: SHA-256 in JGit: why, what, and when – Xing Huang, Google
  • 2:45 PM: GHS: sustaining Git performance under AI workloads – Shane McIntosh, University of Waterloo
  • 3:35 PM: Scaling Gerrit builds with Kubernetes and real-time output sync – Shameer Erakkath Saidumuhammed, Hewlett Packard Enterprise
  • 4:05 PM: How to stack changes like a pro – Jacek Centkowski, SoftwareMill
  • 4:20 PM: Q&A with the maintainers
  • 5:20 PM: Social and networking

Doors open at 9:00 AM.

Stay on for the NVIDIA hackathon, 11–13 November

Straight after the summit, NVIDIA is hosting three days of hacking at its Santa Clara offices. This year there’s one shared goal: making partial clones a practical replacement for Git LFS across the Git and Gerrit ecosystem.

If you develop Git or Gerrit, maintain Git infrastructure, or have run LFS or partial clones in production, your experience is wanted. Spots are limited – email gerrit-hackathon-2026@nvidia.com to reserve one.

Join us in Sunnyvale

Whether you run Gerrit for thousands of developers, contribute to the project, or are working out how code review fits into an AI-driven workflow, this is the room to be in. Seats are limited, so if you’re planning to travel, now’s the time to lock it in.

Register for free on Luma

We can’t wait to see you there.

Why Traditional Git Servers Won’t Survive 2025

Git changed how we build software.

However, the world it was built for – local repositories and teams, along with simple, human-centric CI/CD pipelines – no longer exists.

Today, codebases are massive. Teams are global. And AI is generating code faster than ever before. Our infrastructure hasn’t kept pace, and traditional Git servers are reaching their limits.

Development Has Outgrown Traditional Git

Software development has exploded in both volume and velocity. According to Archive Market Research, the global software repository market will hit $15 billion in revenue in 2025, growing at 15% annually through 2033. GitHub now hosts over 420 million repositories, supporting more than 100 million developers – each pushing more commits, more frequently, and with more automation than ever.

At the same time, 97% of teams now use AI-assisted tools for vibe-coding, AI-agents for creating PRs and commits, automated AI-code-review, and AI-generated documentation. This results in a massive surge in server traffic, particularly read operations from increased test jobs and automated quality-checking processes, which are literally exploding.

Traditional scaling methods – adding more servers, bigger instances, or wider clusters – simply don’t address the core issue: the world has changed since Git was built 20 years ago.

The Breaking Point for Traditional Git Servers

The symptoms are now familiar to most engineering teams:

  • Slow performance. Git clones and fetches are taking several minutes or even timing out instead of completing swiftly in a few seconds.
  • Pipeline delays. CI/CD is waiting for repositories to be available for cloning or fetching, which delays the feedback cycle.
  • Storage capacity strain. Larger monorepos or multi-repo setups are hitting massive BLOB count and hitting ref limits. When storage is hosted on the Cloud or on shared disks, the increase in the directories and I/O transfer makes Git almost unusable.
  • Rising costs. Over-provisioned infrastructure is trying (and failing) to keep up. The provisional or elastic filesystem limits increase significantly, bringing operational costs to new heights never seen before, and putting more pressure on the budget.

The Archive Market Research report warns: “The rising complexity of software development necessitates efficient and reliable repositories for managing code, dependencies, and artifacts.”

In other words, the systems we depend on to deliver software are now slowing software down.

Scaling Smarter, Not Harder

At GerritForge, we believe that simply throwing more hardware at the problem is no longer enough: it is Git and its utilisation that need to be smarter. We have been researching on the use of AI for optimising the performance and scalability of repositories for over 3 years and shared our findings with the global scientific community.

That’s why we built GHS, an AI-powered accelerator for Git-based SCMs.

We have simulated and demonstrated how traditional tools would collapse and developed GHS, a brand-new model to overcome the traditional limitations of the Git repositories.

GHS learns how your repositories behave, your access patterns, your CI/CD workflows, and your traffic peaks – and, using reinforcement learning, automatically optimises performance in real-time.

With GHS, the whole development team will experience:

  • Up to 100× faster Git operations. Clones and fetches keep on completing at raw speed, without slowdowns, timeouts or slack.
  • Real-time auto-optimisation. The Git repositories are automatically monitored and optimised for speed, without manual operations.
  • Lower operational costs. The CPU and storage do not suffer from the overload of incoming traffic, delivering better performance on existing hardware. There is no need to scale up the infrastructure and costs massively.
  • Increased reliability. Git servers remain stable even under extreme load, eliminating the need for emergency restarts or maintenance.

Traditional scaling adds more servers. GHS scales using its sophisticated AI model to get the most out of what you already have.

The Gerrit User Summit 2025 made one thing clear: the era of traditional scaling is coming to an end.

As repositories grow and workflows evolve, the next generation of developer infrastructure must be intelligent, simplified & resilient. AI isn’t replacing developers – it’s augmenting them. But if your Git infrastructure can’t keep pace with this new level of activity, your entire SDLC pipeline will suffer.

2025 marks a turning point for software delivery. Traditional Git servers can’t keep up, but that doesn’t mean your team can’t. Because in modern DevOps, speed isn’t just efficiency, it’s a competitive edge.

Supercharge Your Git with GHS: Experience 100x Faster Performance

Slow Git isn’t just annoying – it’s expensive for everyone: developers wait for a CI/CD validation of their changes, SCM admins are wasting their time in fire-fighting SCM slowdown and broken pipelines, IT managers are wasting millions of dollars in CPU and Disk hosting costs.What if your Git operations could be up to 100x faster, and keep up with the new AI-vibe coding landslide of PR and changes?

100x Faster Git, Powered by AI

GHS is an AI-based accelerator for Git SCM that redefines performance:

  • Up to 100x faster clones and fetches.
  • CI/CD pipelines that run without SCM barriers.
  • Adapt automatically to your repository shape and make it faster.
  • Scale without slowdown even under heavy loads

This isn’t traditional “tuning.” GHS learns your repos and access patterns, then continuously optimises them so your Git server is always running at maximum speed.

How Does GHS Deliver 100x Faster Git?

  1. Measure Everything
    It collects detailed metrics in realtime on your repositories.
  2. Spot Bottlenecks
    GHS AI model is trained on recognizing the bottlenecks and take immediate action, before they become a problem
  3. Stay Fast
    Your Git stays consistently accelerated, not just temporarily boosted.

Why Speed Matters

  • Developers stop wasting hours on slow fetches and builds.
  • Release managers push features out faster.
  • IT leaders reduce infra costs by doing more with less.
  • Admins no longer fire-fight performance issues.

Every 1% of time saved in Git can add up to days of productivity across a large team. Imagine saving 100x that.

Who Needs 100x Faster Git?

  • Repositories of all sizes: AI-driven code generation and “vibe-coding” have dramatically accelerated the pace of software delivery.
  • Enterprises that have adopted the AI-pipeline want that value delivered faster to production.
  • Any team frustrated with slow CI/CD pipelines.

The GHS Advantage

  • Transformative speed: not just 2x or 5x faster, but up to 100x
  • SCM expertise: GerritForge’s decades of enterprise SCM know-how built in.
  • Proven reliability: Stability and uptime as performance scales.

Get Started Today

You can try GHS free for 30 days and experience the difference for yourself.

Why settle for slow Git when you can supercharge it with GHS?