Operations | Monitoring | ITSM | DevOps | Cloud

GitLens 19.4 makes it easier to get into your repository, understand your Git history, and start working without extra setup. The biggest change is simple: the Commit Graph is now available without a GitKraken account for public and local repositories. Open GitLens, open the Graph, and start exploring. No sign-in required. For private repositories, GitLens also gives you a 3-day preview of the Commit Graph without requiring an account, so you can experience the workflow before deciding what comes next.

If your engineering team operates under compliance constraints, code review is about more than catching bugs. It’s where security policies get enforced, audit trails get documented, and institutional knowledge gets shared. Choosing the right code review platform determines how quickly your developers move from pull request to production. GitKraken gives enterprise development teams a unified DevEx platform that connects code review, pull request management, and collaboration into a single workflow.

If your team runs on Jira, the Git platform you choose can either accelerate your workflow or slow it to a crawl. Commits that never show up in your sprint board, branches that don’t link back to tickets, and pull requests that exist in a parallel universe from your backlog: these are the friction points that stack up fast for Jira-centered teams.

AI coding agents are rewriting the rules of software development, but running multiple agents across a real codebase creates a coordination challenge that traditional editors and terminals weren’t built to solve. That’s where agentic development environments come in. An agentic development environment (ADE) gives you a dedicated surface for launching, orchestrating, and reviewing the work of several AI coding agents at once.

A Git merge conflict happens when two branches edit the same line of code in different ways. Git can’t decide which version to keep, so it pauses the merge and asks you to step in. The longer a conflict sits unresolved, the harder it becomes to untangle. This guide walks you through eight clear steps to identify, fix, and verify merge conflicts during your branch merging workflow. GitKraken gives you a visual merge tool that turns this process from guesswork into a few confident clicks.

Your team ships more code than ever, but are your pull requests keeping pace? As AI-assisted development accelerates output, code review collaboration platforms have become the difference between shipping confidently and merging blindly. The right platform connects your review workflows, surfaces context where you need it, and keeps collaboration flowing across distributed teams.

Your distributed team just merged three branches at once, and the commit graph looks like a plate of spaghetti. Choosing the right version control platform determines whether that scenario ends in a five-minute fix or a full afternoon of detective work. GitKraken gives you a visual, cross-platform approach to Git that turns complex repository management into a clear, collaborative workflow.

Running one AI coding agent is productive. Running five of them at once across three repositories? That’s a coordination problem. Agentic development environments (ADEs) give you a single surface to orchestrate multiple agents, review what each one changed, and get code merged. Kepler by GitKraken is one of the most capable options in this growing category. It’s built around agent-agnostic orchestration and Git workflow control from backlog to merged PR.

Code review in a Jira-centric workflow can become a bottleneck fast. Pull requests pile up, context gets lost between your Git host and your issue tracker, and reviewers spend time switching tabs instead of reading code. The right code review platform should connect Git activity directly to the issues you’re tracking.

I built GitBench because I was curious about how well models did git things. It turns out that it was a good idea because some models will surprise you. Some of the frontier models were remarkably bad and some cheap open models punched above their weight class. But, as they say, “the times they are a changin’”. Before I go too deep into the latest results, you may want to read up on GitBench and what it is and why I built it in the previous blog post.