Recent releases have added some genuinely useful features. AI Commits let you generate commit messages and descriptions with one click, right from the commit area — handy for when writing a good commit message is the last thing you feel like doing. Automatic Branch Archiving takes care of housekeeping by detecting stale or fully merged branches and archiving them for you, so your sidebar doesn't fill up with clutter over time.

For teams with their own conventions, Custom Git Workflows let you define a branching model from scratch — trunk/topic branches, prefixes, merge strategies — or start from templates like git-flow or GitHub Flow, with one-click "Start/Finish Feature" actions to guide you through it. Tower also has Graphite Integration built in, covering stack creation, restacking, PR submission, and merge queue support without leaving the app.

Two more additions support more advanced setups: Worktree Support, for checking out and working on multiple branches at once, and Stacked Branches, which track parent-child relationships between branches so you can work with stacked pull requests and restack a whole chain with a single action.

Rounding things out, Commit Templates let teams reuse commit message formats across a repository, with quick keyboard access when you need one.

I wanted to learn Kubernetes, but the options were either "build a local lab" or pay for expensive classes built around cloud environments. I wanted something you could just open and learn from. So I built a browser-based cluster simulation with lessons to follow along.

It behaves like Kubernetes, but it's just JavaScript under the hood. Enough to run kubectl commands, create resources, and watch their lifecycle play out. There's also a live cluster visualizer so you can see your nodes, Pods, and containers in real time.

Once you've covered the concepts, you can jump into CKA drills. Each drill is a standalone, time-boxed scenario that mirrors the real exam format: a broken cluster state, a concrete task, and a pass-or-fail outcome.

The goal isn't to simulate the exam. It's to build the reflex of diagnosing and fixing things quickly, so that when you sit the real exam, the commands and the reasoning are already automatic.