GitKraken Desktop 12.7.0 is out. If you skim the release notes, you’ll see some bug fixes and not much else. But for those of us who work on GitKraken Desktop, this is one of the biggest releases we’ve ever shipped: as of 12.7.0, NodeGit is no longer used for any git operations. Every git operation in GitKraken Desktop now runs on core git, the same git you use in your terminal.
That probably sounds like a strange thing to get excited about. So let me explain what NodeGit is, why we built on it in the first place, and why it took us five years to move off it.
NodeGit is a library that lets Node.js code call libgit2, a standalone implementation of git written in C.
When we started building GitKraken Desktop in 2014, the git command line tools didn’t give us much to work with. There weren’t many options for tweaking how an operation ran, and most of the output was meant for a human to read, which made it hard for a program to parse reliably. NodeGit gave us direct access to the repository instead. That was a big part of how GitKraken Desktop could do more than other git clients of the time.
Fast-forward to about 2020. Big players (mostly Microsoft) started investing hugely in core git, and options were getting added for the exact things we had needed back in 2014.
And right as more of our customers were working in very large repositories, git was landing new large-repo optimizations every few months. Those optimizations go into git itself. libgit2 is an independent implementation, so it doesn’t get them unless someone does the work to add them there too. For us, keeping up would have meant Microsoft-level investment in a library that wasn’t our product.
One of our other early decisions presented a second problem. GitKraken Desktop is built on Electron, and keeping NodeGit compatible with Electron was getting harder with every release.
By late 2021, it was clear to us that NodeGit wasn’t our future. We decided to stop relying on it and put that effort into the things that make GitKraken Desktop worth using.
While the decision came quickly, the work took way way longer. GitKraken Desktop had been built on NodeGit for seven years at that point, so nearly every feature touched it somewhere. We also couldn’t stop shipping releases while we rewrote the foundation, so the move happened piece by piece, alongside everything else on the roadmap.
Ask anyone who has spent a long time in the GitKraken Desktop codebase, and they’ll tell you what a big deal this is. We couldn’t have finished it without years of work from a lot of talented engineers. (If you’re reading this, kudos to the dedicated effort, my friends).
Okay okay, so what does this mean for you? In day-to-day use, you shouldn’t notice a difference, and that was the goal.
The difference is in where our time goes. For years, part of our engineering time went to keeping NodeGit working instead of building things for you. That time now goes to GitKraken Desktop itself. And because we’re on core git, the work the git community puts into git (including all those large-repo improvements) is work we can build on directly, instead of rebuilding it ourselves.
We still have a bit of clean-up left: NodeGit will be fully removed from dead code paths and our build system soon. After that, the first thing we’re putting the freed-up engineering time toward is performance, since it’s one of the things you ask us for most.
GitKraken MCP
GitKraken Insights