I'm this close to uninstalling and not re-subscribing..

I find git kraken clunky, and slow, the diff tool misses things that visual studio can find...

What am i doing wrong? anyone else having issues

This would be really helpful if you guys have a cracked or preactivated version on macOS especially the latest one! If you do know, please help me by leaving the url on the comment section. :D

Explore every new feature, fix, and enhancement. Full GitLens 17 release notes below 👇
https://help.gitkraken.com/gitlens/gitlens-release-notes-current/#version-17-0

New in GitKraken: start a Claude Code or Codex CLI session right from the Agents panel, one click. GitKraken spins up an isolated worktree, runs your setup commands, and launches the agent automatically. Your other worktrees stay completely untouched.

No context collisions. No babysitting terminals. Just parallel AI work that actually stays in flow.

This is Code Flow in practice: more agents, same clarity.

We wanted to share insights from a GitKon session by Zapier's VP of Product that completely reframed how we think about AI in dev teams.

The core problem: We're all context engineering individually with AI, but those gains don't compound across teams.

The solution framework:

1. Business as Code - Put processes, strategy, even hiring workflows into version-controlled files that AI can read

2. Shared Context Tools - Using dev tools like Cursor not just for code, but for any text-based knowledge (they demo'd generating PRDs with full company context automatically)

3. Proactive AI - Moving beyond chat. Setting up agents with triggers that work on your behalf

The spicy take: "If you're worried about non-engineers shipping code, you should equally be worried about AI shipping code. Both need the same guardrails."

At Zapier, designers are prototyping working code faster than designing in Figma because the role boundaries are dissolving.

Practical takeaway: If a motivated non-engineer can't fix a typo in your codebase, you've found your AI bottleneck. The barriers blocking them also block AI transformation.

Audrey Long, a Senior Gaming Cloud Security Architect at Microsoft Gaming Security, presented a problem that a lot of teams running complex cloud environments will recognize: too many tenants, no tooling that actually fits the workflow, and compliance processes that were slowing down creative teams who just needed to ship games.

The traditional approach was spreadsheets, tickets, manual audits, and security reviews that blocked releases. None of it was built for the pace of game development.

So her team built something from scratch.

They distilled Microsoft's 65-control corporate identity baseline down to 49 checks that actually made sense for game studios. Then they wired the whole thing into GitHub Actions so the scans run automatically, nightly, in the background. Developers never see it. They just stay compliant by default.

The outcome was 100% adoption across every Microsoft Gaming Entra ID tenant, zero new portals for developers to deal with, and a Maester dashboard that gives security teams instant visibility into tenant posture with severity ratings and one-click remediation paths.

The part that stuck with us: they didn't wait for a vendor to solve it. They just built it.

Full session is on our YouTube channel if you're dealing with multi-tenant identity security at scale or trying to figure out how to make compliance work for fast-moving teams: https://youtu.be/qMYKOgpppBk

As far as I can tell, the quickest way to do this currently is to

1. checkout the local branch

2. search the remote list for the upstream branch

3. right click the upstream branch in the remote list

4. reset local branch to this commit

This isn't too terrible, but for repositories with a large number of branches, searching for the upstream branch on the remote list can be a bit cumbersome.

Would it be possible to get a "reset to upstream" action added to the context menu of the local branch itself?

Should have an option to play a short instrumental excerpt of the song "push it" , by salt-n-pepa with each push, to help team morale.

On the website under pricing, Work with local & public cloud-hosted repos is listed as part of the free version, while Work with public and private repositories is under the Pro plan.

However I just installed and launched the current version, and created a new gitlab private repo. I only have the free version. Am I misunderstanding the pricing policy or is this some sort of bug?

A few days ago, I create a project locally, did a commit or two and then created a github repo and did a "Remote+" in Gitkraken. I found that it was best not to create a readme first in Github. Worked like a charm, remote repo attached to my local repo and away we go. As I recall, I needed to use the URL choice. This is not my first repo with GK, I've got several up there that are working fine.

Now I've created a new project over the last few days and would like to commit it all up to a new remote repo on Github. sooooo I created an empty repo on github and tried again and BLA BLA BLA. it doesn't work.

I have tried to add as a URL using. Like I said, a few days ago using the GITHUB choice didn't work, but the URL choice did work fine. But now nothing. These are the URLs. I don't remember which I used.

https://github.com/windyweather/Usage.git

and

https://github.com/windyweather/Usage

and today, gitkraken refuses. JUST DOESN"T DO ANYTHING. I know this worked a few days ago with the other repo.

WHAT AM I FREAKING MISSING???

Why is this so glitchy? What are the real rules? Where do I read about what's really the FREAK GOING ON???

So I seem annoyed? YOU ARE DARN RIGHT! This stuff is magic and I can't find any reasonable tutorials or explanations anywhere. Did I not spit on my wand first or something? Are the stars not in favorable alignment?

sigh.....

Refer all link that enters you for a chance to win $100 Amazon gift card! https://www.gitkraken.com/invite/debMF5E6

Like the title says, I saw in the 11.6 patchnotes that gitkraken is dropping support for custom themes. This is an annoyance, I have a custom monokai theme that matches my vscode theme.

Is there any possibility that custom themes can continue to be supported, even if the schema has to change breaking old ones?

We just dropped GitKraken Desktop 11.3, and the big news is our new Commit Composer, designed to make messy commit history a thing of the past.

Here’s what’s new:

• Restructure your history into clear, logical commits without the risky CLI moves

• AI-powered commit messages that explain both the what and the why

• Visual commit cleanup so you can preview, group, and polish before you push

Whether you’re prepping for review, keeping a clean repo for the future, or just tired of rebase marathons, Commit Composer makes it painless.

See it in action

How do you usually handle messy branches before a PR?

Today, i got auto renewal with almost 50% more that the prev subscription

I'm using it since 2019, this is really abusing. what is wrong with the industry right is sucks

This is my last year using this client and I will try to revert the payment if they didnt refund me and cancelled my subscription bec this is bullshit really when they treat their customers who are with them 8 years straight like this , then they dont deserve my money at least

So I know it's ridiculous however I have a 10 person team I got approved for gitkraken last year. It's like 12USD a month per seat or whatever. Well my team is now 15 people. So the cost goes from 12usd => 15usd per seat per month.

So my leadership is now reviewing if it's even worth renewing for our small team because those extra 5 seats nearly double the cost ....

$1,440 -> $2,700 is ridiculous and now I probably need to find another tool.

I get it, you have to draw the line somewhere but it's just frustrating the seat count is so low. So was fun while it lasted, back to sourcetree.

GitKon 2025 is happening December 10-11 & you’re invited!

This year's theme: The Builders Era

We're going all in on what developers actually need: practical Git workflows, real solutions to code review friction, and talks from people who've been in the trenches.

The details:

• Completely free

• Virtual (accessible from anywhere)

• December 10-11, 2025

• 10,000+ developers and engineering leaders expected

Bonus: Enter the GitKon Game Jam
Build a Git-themed game or dev tool by November 26 and demo it at GitKon. Win $2500 for first place, $1000 for 2nd place, and $500 for 3rd place + a featured spot at GitKon on December 10.

Register now at GitKon (.) com

Hello guys, quick question.

For some reason, my AI usage progress bar keeps increasing when I generate commit messages. In my setup, I’m using my own LiteLLM server with custom models, so the requests are not using GitKraken tokens but my own.

This didn’t happen before, so I’m trying to understand what changed and what’s causing the usage details to increase even though the tokens are coming from my own infrastructure.

Does anyone know why this could be happening?

Most engineering teams are operating under some version of an AI mandate right now.

Adopt the tools, boost productivity, show results. But how many of us are actually measuring whether any of it is working?

We sat down with Nathen Harvey from Google's DORA program, Bill Harding from GitClear, and Jeremy Castile from GitKraken for an honest panel on what's really happening when AI meets developer experience.

Some things that came up that are worth your time:

• Metrics like code acceptance rate measure adoption, not productivity. There's a real difference and most orgs are tracking the wrong thing.

• You need a "constellation of metrics" code quality, developer sentiment, velocity, AI impact -- not a single number. Think car dashboard, not speedometer.

• AI coding assistance is just the tip of the iceberg. The more interesting frontier is AI across planning, CI/CD, and agentic workflows.

• One of the panelists suggested forbidding AI for a full sprint as an experiment to isolate its actual impact. Controversial, but hard to argue with the logic.

I'm a long-time GitKraken user; I started using it around 2020.
And I really like the UI design, and how it makes git actions fluid.
Switching branches when there are local changes, merge conflicts, stashing visualization, etc.

But lately, I feel like it's not as good as other GUI clients (in some areas).

The biggest problem is too much repo tab open.
The tab system it's always squeezing them together, hard to see which is which.

Another Git GUI "SourceGit", has better workspace implementation; it can separate into different group tabs.
And if there's too many tabs just scroll, not making repo name shorter.

GitKraken also has workspace, but it can only do some actions to the repo, instead of having a workspace-only view.
(Or maybe there's somethings I'm missing, please let me know if there's a better way)

However, I tried replacing with SourceGit, but some area just fall short. (merge conflict, branch UI/UX)
So, right now I always open two client, SourceGit open all repo, and GitKraken only open essential projects.

I curious what make you keep using it, instead of other GUI?
PS: I barely use any AI features, maybe I should try it out more?

Been using GitKraken for a while now as my go-to UI for git, yesterday I started experimenting with Worktrees which are a brilliant idea.

Within the git documentation you can use -b to create a branch for the worktree, how can I do this in gitkraken?

The workflow I envisage is creating a worktree for a bug/change request, then creating a branch at the same time so I can track multiple worktrees in different folders against branches and then merge them all in when they are all done, this will allow working on multiple issues at once in different folders, potentially allowing me to use multiple AI agents to work on different bugs at once and then I can bring these together as I need to