If you’re a developer, you know this story.
You open your terminal, run a few Git commands, and suddenly your branch looks like spaghetti 🍝. Merge conflicts? Detached HEAD state? Submodules pulling you in five directions at once? Yeah, we’ve all been there.
That’s why I’ve been having a lot of fun lately experimenting with GitKraken. At first, I thought it was “just another Git tool”, but honestly, it’s much more than that.
Want to Try It?
If Git has ever made you scratch your head (or bang it against the desk 😅), I highly recommend giving GitKraken a shot.
👉 You can grab it here — and full disclosure, if you sign up through this link, you’ll get 50% off, and we both get a little reward. Win-win
Here is a video for you to watch how it works:
The Power of Seeing Your Git History
What makes GitKraken special is its visual graph. Instead of trying to mentally trace commits from the CLI, GitKraken lays them out in a clean, colorful, and interactive UI.
You see branches split and merge in real-time.
It’s super easy to drag, drop, and resolve conflicts visually.
And if you’re dealing with something painful like multiple submodules (hello, Moodle devs 👋), GitKraken makes it way less intimidating by showing relationships clearly.
For me, this was a game changer. With Moodle’s complex codebase and submodules, GitKraken helped me understand what was going on without constantly flipping between docs and terminal.
Complete version of this article can be found here
Top comments (0)