Operations | Monitoring | ITSM | DevOps | Cloud

Tasteful AI features? Is that even a thing? With GitKraken Desktop 11.1, we think we’ve struck the right balance of adding useful AI capabilities that stay out of your way until you actually need them. In our previous release, we introduced GitKraken AI, which helps explain selected commits and generate commit messages. With 11.1, we’re building on that foundation with two major enhancements that bring even more context-aware assistance to your workflow.

Written by author, adapted by AI GitKraken Desktop 11.0 is here, and it’s more than just a version bump. We’re introducing AI-powered features designed to accompany your workflow and help you stay focused on what matters most. It’s changed how I approach commits, and I’m sure it will help y’all too!

GitLens 17.0 delivers a transformative update that revolutionizes Git workflows directly within Visual Studio Code. This release introduces GitKraken AI, native Bitbucket integration, and advanced multi-commit capabilities designed to eliminate friction points throughout your development process.

We recently started the Public Preview for a ground up rewrite of the GitKraken CLI. You might be wondering, “why?” We needed to rapidly iterate on a brand new idea, the “Work Item”. We also learned a lot from the previous iterations and realized a fresh start could help us optimize the user experience around the most precious resource, time.

Software development is changing fast, and here at GitKraken, we’re excited to be at the forefront. We’re entering a new era—one where AI is helping developers rather than trying to replace them. Our goal is to put that power to work for developers—embedded in your workflows, on your terms. We’ve been listening closely to feedback from our community—developers, team leads, engineering managers, and our enterprise customers.

Developing a website or software isn't easy, a team of developers will be developing a new feature, other team will be testing whether the built feature works as expected, other might be fixing the bugs and so on. Managing these different versions of same code base must be a little tricky. Here comes the concept called branch in git which is used as a pointer to a snapshot of your changes. When we talk about branches in git these are the major questions that arises in our mind.

Git is a terrific tool that many developers use to keep track of their projects’ versions. Despite the fact that there are many different version control systems, git is by far the most used. The focus on distributed development and the ease with which branches can be used for good reasons.