@GitKraken

GitKraken’s DevEx platform orchestrates workflows between devs & AI to save time & boost productivity. Powering 50M+ devs at 100K orgs 🚀

 Scottsdale, AZ
linktr.ee/gitkraken
Joined March 2015
  • Tweets10.6K
  • Following211
  • Followers17.1K
4.1KMedia
Unpopular opinion: Being a senior engineer has almost nothing to do with writing code. It’s about communication, unblocking your team, and making decisions when there is no "right" answer.
1
282
Git Forensics in GitKraken: Reading What Your Teammate Actually Did — A teammate new to GitHub leaves four classic Git mistakes on the remote -- a commit straight to main, a branch off the wrong branch, a ladder of merges, ... holgerscode.com/blog/gitkrak… @GitKraken

Git Forensics in GitKraken: Reading What Your Teammate Actually Did

A teammate new to GitHub leaves four classic Git mistakes on the remote -- a commit straight to main, a branch off the wrong branch, a ladder of merges, and every commit twice -- and we read each one...

holgerscode.com
2
2
133
Punk solutions to modern problems! Thanks @GitKraken!
1
3
137
If you've typed the same prompt to an agent twice, it should be a button. Kepler Actions are named prompts you fire at a task, issue, or PR. You can edit the built-ins, write your own, and pin each one to a different model. help.gitkraken.com/kepler/ac…
1
276
84% of devs say AI makes them more productive. 39% of their orgs have no way to measure it. Another 33% just ask the devs. New data from 554 devs and engineering leaders: gitkraken.com/reports/state-…
1
3
350
GitKraken retweeted
Mr_SC@Zelig880Oct 9
Have you ever tried to maintain 12 branches aligned? Well I did for my book and without @GitKraken I would have been lost! Luckily its Commit Graph is just so beautiful, making maintaining this aligned a simple task!
1
3
398
GitKraken retweeted
Alisson Nunes@AlynvaOct 9
Replying to @tsoding
If you use a good git client like @GitKraken , you would know very well this feature
1
1
255
Borré una rama y Git se negó: seguía abierta en un worktree. GitLens 19.3 (1 de octubre) ahora borra rama y worktree en un solo confirm, con Delete Branch pre-marcado. Lo contrasté hoy con las release notes oficiales. @gitkraken #GitLens #Git
1
1
1
192
Next.js Merge Conflicts in GitKraken: One Real Conflict, Step by Step — A real merge conflict in a Next.js header -- two teammates, three conflicting hunks, one lockfile -- resolved step by step in GitKraken Desktop holgerscode.com/blog/nextjs-… #GitKraken #Git @GitKraken

Next.js Merge Conflicts in GitKraken: One Real Conflict, Step by Step

A real merge conflict in a Next.js header -- two teammates, three conflicting hunks, one lockfile -- resolved step by step in GitKraken Desktop, including the resolution that passes the build and...

holgerscode.com
1
2
152
Interesting read. Are your AI processes as efficient as you think they are?
GitKraken
@GitKrakenOct 7
Only 24% of devs we surveyed can prove their AI agents are paying off. 45% are going on gut feel. 21% can't tell. 8% say they're spending more without moving faster. Here's what else they told us about agent cost and ROI 👇
1
2
152
Replying to @GitKraken
@GitKraken, just see how Kepler is evolving, and that's fantastic! Great job team 🚀 And great webinar 🎉
1
1
166
GitKraken retweeted
GitLens@gitlensOct 7
GitLens 19.3 is here 🦑 Start work directly in Kepler. Rebase an entire stack of PRs at once. Let AI handle conflicts across the stack. And start working from GitLens even when you don't have a repo open. Let's get into it 👇
1
1
1
185
Yess Gyo!
Gyo Piazza@gyopiazzaOct 7
I've always been shy about sharing work in public, not sure why But now I need to, I'm too proud of what we're building together with a team of rockstars @GitKraken Kepler is not just a tool I help building, it's what I always needed to manage agents gitkraken.com/kepler

Kepler | Mission Control for Agent-driven Development

Kepler is GitKraken's agentic development environment. It gives developers full clarity and control to run parallel agents at scale: plan work, write code, and review what ships, all from one surface.

gitkraken.com
1
600
Only 24% of devs we surveyed can prove their AI agents are paying off. 45% are going on gut feel. 21% can't tell. 8% say they're spending more without moving faster. Here's what else they told us about agent cost and ROI 👇
1
1
1
5
467
Before you hand an AI agent your merge conflicts, check how it scores on Git. @cmgriffing's 18-minute tour of GitBench: model comparisons, reasoning levels, token usage. The repo is public, so you can run it against your own models. youtu.be/y7Oug2rNB-s
1
1
443
Running more agents doesn't help if every task still starts with a blank prompt. Tomorrow we're showing how to turn agent workflows that work into reusable patterns with Kepler and Insights for Developers. Register to win a portable monitor: gitkraken.com/webinar/scale-…
1
1
339
Running five agents across twelve branches and trying to figure out what's ready to merge? Kepler runs Claude Code, Codex, Copilot, and Cursor in parallel, each in its own worktree, and shows you every agent's work on one graph. gitkraken.com/kepler
4
1
5
681
Your agents write code in minutes. Your review queue didn't get the memo. We built workflows for the new bottleneck: managing agents, reviewing AI-generated code, knowing what's safe to merge, and untangling the conflicts parallel work creates. gitkraken.com/lp/workflows
1
468
GitKraken retweeted
John Ennis
@johnennisSep 29
I would be so unbelievably fucked without @GitKraken I don't understand how anyone lives without it
7
1
20
2,888
Four lines in a CLAUDE.md file can change how an AI assistant works in your codebase. Tell it your review standards, naming conventions, architectural boundaries, and definition of done, and it stops generating code that needs heavy rework before it's review-ready. That's Code Flow thinking applied to AI config: don't just optimize for what the AI writes, optimize for what your pipeline can actually handle. We build the pipeline that makes those four lines matter. #CodeFlow
1
517
Load more