20 Years of Git, 2 days at GitHub HQ: Git Merge 2025 highlights 🎉

Git Merge 2025 celebrated 20 years of Git with talks, collaboration, and community. Catch the highlights and recordings.

GitHub’s PJ Metz speaks on stage in the GitHub HQ auditorium, addressing a large audience seated on tiered benches. The space features exposed beams, plants, and a hanging green Invertocat installation overhead.
| 3 minutes

Two decades after Linus’s first git commit, contributors from around the world gathered at GitHub HQ in San Francisco—not just to reflect on Git’s history, but to imagine its future. Git Merge 2025 marked 20 years of Git with technical talks, community collaboration, and the kind of hallway chats you can’t capture in slides. More than 100 people joined us in person, and over 600 tuned in online.

Day 1: Talks for everyone

From deep dives into Git internals to beginner-friendly sessions on creative workflows, this year’s program offered something for everyone. We heard from maintainers, educators, hobbyists, and even a high school student, sharing how Git shapes their work and learning. Speakers joined both in person and remotely from around the globe, making this one of our most accessible and inclusive Git Merge events yet.

People seated around a long conference table at GitHub HQ’s Executive Briefing Center during the Git Contributors Summit. Laptops are open, and several participants join remotely on large screens at the front of the room.
Attendees gathered in the GitHub HQ amphitheater during Git Merge 2025.

Scott Chacon mixed comedy and code in a live demo of the GitButler CLI, while Google’s Martin von Zweigbergk unpacked how Jujutsu integrates with Git. Jacob Stopak reimagined Git learning through visualization and gamification, Steffen Hiller and Zoran Petrovic showcased new ways to visualize how repositories grow over time, and brian m. carlson unpacked what’s next for SHA-256 interoperability. Explore the playlist to watch these talks and more!

Day 2: Community at the center

The second day focused on collaboration with the annual Git Contributor’s Summit and an Unconference. Core maintainers and contributors met, both in person and remotely, to shape Git’s roadmap for the year ahead in one of our most remote-friendly gatherings yet. 

People seated around a long conference table at GitHub HQ’s Executive Briefing Center during the Git Contributors Summit. Laptops are open, and several participants join remotely on large screens at the front of the room.
Git Contributor’s Summit

During the summit, our Unconference opened the floor to everyone, with whiteboards filling quickly with ideas on branching strategies, Git education, and creative workflows.

Thank you

Git Merge 2025 wouldn’t have happened without this community. From the speakers who shared their work, to the contributors and volunteers who gave their time, to every attendee who showed up ready to learn and connect… thank you. 

Huge thanks to the GitHub teams behind the scenes who made the event seamless for attendees around the world. 

And a special thanks to our sponsors, GitButler and Google, for helping bring this year’s celebration to life. 

Until the next Git Merge, keep committing. <3

Catch up on the talks from Git Merge 2025 >

Written by

Lee Reilly

Lee Reilly

@leereilly

Senior Program Manager, GitHub Developer Relations. Open source hype man, AI whisperer, hackathon and game jam wrangler. I write && manage programs, support dev communities, and occasionally ship something.

Related posts

Git Merge 2022 – that’s a wrap! 🎬

Git Merge 2022 just wrapped up bringing the community together for 16 talks, three workshops, one Git Contributor Summit, and lots of great conversations over two days. Read on for more info, photos from the event, and all of the session recordings.

Mission report: Git Merge 2019

This year, Git Merge went to Brussels to host two days of all things Git. The event brought together hundreds of business leaders, source control teams, and developers—people who have a vested interest in Git and companies that hire Git contributors.