|
By Jade Nangah
Merge conflicts rarely make it into a sprint retrospective, but they should. They’re one of the most reliable ways to lose an hour of flow without anyone noticing it’s gone. Every developer expects them eventually, but almost nobody questions the workflow around resolving them.
|
By Chris Griffing
GitBench is our attempt to see how well LLMs handle git-specific tasks. We put together a suite of 17 benchmark categories with a total of 204 specific test cases. We ran these benchmarks against 43 (and counting) different models with all of their supported effort/reasoning levels.
|
By Matt Johnston
From plan to main. Software is no longer just a tool. It is the infrastructure of modern life. Software keeps airplanes in the sky and power flowing into our homes. It helps doctors save lives, scientists discover cures, farmers feed cities, and astronauts navigate space. It powers economies, protects supply chains, and connects billions of people across the world. Every major system humanity depends on now depends on software. Which means developers are no longer just building applications.
|
By Jade Nangah
You’re no longer writing code. You’re managing a pipeline of agents writing it for you. If you’ve been running two, three, or four AI coding agents in parallel, you already know the problem. The agents are fast. The orchestration is chaos. You’re bouncing between terminal windows, manually rebasing branches, cleaning up messy commits, and trying to remember which agent is touching which repo.
|
By Jade Nangah
Your pull request has been open for three days. Your reviewer hasn’t commented. You’re starting to wonder if anyone will ever look at it—and whether the code you wrote on Monday still makes sense on Thursday. This feeling is common. PR lifecycle time—the duration from first commit to merged code—directly impacts how quickly you ship features, how fresh your code stays, and how engaged your reviewers remain.
|
By Jade Nangah
Tracking down who made a specific change in your codebase can feel like detective work. Whether you’re debugging an issue or trying to understand why a particular piece of logic exists, knowing the history behind each line is invaluable. GitKraken makes this process simple with tools like GitLens for VS Code and GitKraken Desktop, which bring blame annotations directly into your workflow.
|
By Jade Nangah
Engineering leaders need more than raw metrics, they need actionable insights they can trust with their data. When evaluating engineering intelligence platforms, privacy controls and centralized repository oversight should top your criteria list. The platforms on this list each offer distinct approaches to tracking DORA metrics, developer productivity, and code quality while keeping your data secure.
|
By Jeff Schinella
The Agent Impact Leaderboard and the Business Impact & ROI Dashboard are live in preview inside GitKraken Insights today. We built them because the questions engineering leaders are getting asked about AI shifted faster than the tools to answer them. Here’s what shipped and how to get access.
|
By Chris Griffing
If you are a software developer or engineer, you most likely have to do code review. At the bare minimum, you probably have had your pull requests reviewed. If you haven’t, then you are probably curious about how the rest of the world deals with the process. In general, we use code review to make sure we are shipping high quality code that does what it’s supposed to and is easy to maintain. That’s the goal, at least. In practice, code review can get messy.
|
By Jade Nangah
Choosing the right Git extension for your VS Code setup can make the difference between a smooth workflow and hours lost hunting for context. GitLens, developed by GitKraken, and VS Code Git Graph both aim to enhance your Git experience, but they approach the problem differently. This article ranks both extensions across key workflow scenarios – merge conflicts, commit history, code review, debugging, UX, and performance – so you can pick the right tool for how you work.
|
By GitKraken
New: launch a Claude Code or Codex CLI session straight from the Agents panel. One click → isolated worktree → setup commands run → agent starts. Your other worktrees don't even notice. Parallel AI agents without the chaos. That's code flow.
|
By GitKraken
AI adoption is easy to report. Business impact is harder to prove. Engineering leaders are under pressure to show what AI is actually changing — not just who is using it, but whether it is improving delivery, quality, developer experience, and business outcomes. This discussion between 3 engineering leaders explores how to move beyond vanity metrics, build a practical measurement approach, and communicate AI’s value to executives and CFOs with more credibility and less hype.
|
By GitKraken
GitKraken Desktop gives you a visual Git client and AI coding agent hub in the same window. Manage branches, PRs, and conflicts on the Commit Graph while running Claude Code, Copilot, Codex, or Gemini in separate worktrees. Available on Windows, Mac, and Linux.
|
By GitKraken
AI tools are spreading across the entire software development lifecycle - but are they actually making developers more productive, or just adding noise? In this panel from Context Conference, Najla Elmachtoub (Squadformers) moderates a sharp, no-fluff conversation with Nathen Harvey (Google, DORA program), Bill Harding (GitClear), and Jeremy Castile (GitKraken) on what's really working when it comes to AI and developer experience.
|
By GitKraken
Kepler is GitKraken's agentic development environment: mission control for running parallel coding agents at scale. Running one agent is easy. Running five of them across three repos is where things break: scattered terminals, no shared view, no idea what's done or stuck. Kepler puts every agent session on one surface so you can plan work, write code, and review what ships without losing track of anything.
|
By GitKraken
Developer experience predicts what's coming 3 to 6 months before it shows up in your delivery metrics. So why are most engineering leaders measuring it last? In this session, GitKraken VP of Developer Research Jeremy Castile breaks down what developer experience (DevX) actually is, how to measure it across 6 key dimensions, and how it connects to velocity, code quality, and AI impact data your team is already tracking.
|
By GitKraken
AI developer productivity, agentic workflows, and the lessons learned running engineering tools for 100,000+ software engineers at Google. John Montgomery, CCO at GitKraken, sits down with Asim Hussain, co-founder of Alterion AI and former Google VP of Engineering Productivity, to get real about what AI actually changes for engineering teams in 2025.
|
By GitKraken
AI tools are spreading across the entire software development lifecycle - but are they actually making developers more productive, or just adding noise? In this panel from Context Conference, Najla Elmachtoub (Squadformers) moderates a sharp, no-fluff conversation with Nathen Harvey (Google, DORA program), Bill Harding (GitClear), and Jeremy Castile (GitKraken) on what's really working when it comes to AI and developer experience.
|
By GitKraken
AI developer productivity, agentic workflows, and the lessons learned running engineering tools for 100,000+ software engineers at Google. John Montgomery, CCO at GitKraken, sits down with Asim Hussain, co-founder of Alterion AI and former Google VP of Engineering Productivity, to get real about what AI actually changes for engineering teams in 2025.
- July 2026 (4)
- June 2026 (7)
- May 2026 (20)
- April 2026 (12)
- March 2026 (13)
- February 2026 (10)
- January 2026 (11)
- December 2025 (2)
- November 2025 (11)
- October 2025 (15)
- September 2025 (10)
- August 2025 (10)
- July 2025 (20)
- June 2025 (8)
- May 2025 (5)
- April 2025 (3)
- March 2025 (9)
- February 2025 (6)
- January 2025 (14)
- December 2024 (6)
- November 2024 (18)
- October 2024 (10)
- September 2024 (19)
- August 2024 (6)
- July 2024 (27)
- June 2024 (27)
- May 2024 (26)
- April 2024 (29)
- March 2024 (28)
- February 2024 (27)
- January 2024 (16)
- December 2023 (29)
- November 2023 (22)
- October 2023 (8)
- September 2023 (9)
- August 2023 (7)
- July 2023 (2)
- June 2023 (2)
- May 2023 (4)
- April 2023 (5)
- March 2023 (5)
- February 2023 (6)
- January 2023 (10)
- December 2022 (3)
- November 2022 (2)
- October 2022 (3)
- September 2022 (5)
- August 2022 (3)
- July 2022 (4)
- June 2022 (5)
- May 2022 (5)
- April 2022 (6)
- March 2022 (4)
- February 2022 (4)
- December 2021 (4)
- November 2021 (15)
- October 2021 (2)
- September 2021 (6)
- August 2021 (1)
- July 2021 (4)
- June 2021 (1)
- May 2021 (2)
- January 2021 (3)
- November 2020 (2)
- October 2020 (3)
- September 2020 (2)
- August 2020 (3)
- July 2020 (3)
- June 2020 (3)
- May 2020 (2)
- April 2020 (3)
- March 2020 (4)
- February 2020 (5)
- January 2020 (5)
- December 2019 (2)
- November 2019 (3)
- October 2019 (1)
- September 2019 (2)
- August 2019 (3)
GitKraken is on a mission to make Git easier, safer and more powerful across multiple surfaces and environments that development teams use.
Over 10 million developers from more than 100,000 organizations worldwide rely on GitKraken to get their work done. Since 2014, we've been rapidly developing the legendary cross-platform tools while reimagining an intuitive, visual approach to Git. Our team is dedicated to making tools that help software developers be more productive using Git, it's truly our passion. We develop software that's in use by the world's most elite companies like Apple, Google, Microsoft, Amazon, and thousands of other leading organizations.
We Make Git Tools Devs Love.