If you've been using stackit log to see your stack, there's a change coming in the next release you'll want to know about. I've reshuffled the navigation verbs to better match the mental model from git.

What changed

stackit log is now stackit tree ⚠️ (breaking)

The command that draws your branch graph is now called tree. That's really what it always showed, a tree of branches, and calling it log fought against everyone's git log instinct, where log means commit history. The full and short subcommands come along for the ride:

stackit tree # the branch graph you know
stackit tree short # the compact view
stackit t # new short alias for `tree short`

stackit log now means what you'd expect

We freed up the log verb for a new, stack-aware trunk commit history. It collapses each consolidated stack-merge into a single entry that lists its constituent PRs - the same view as the web app's "Recently Merged" panel (I'm quite proud of that panel).

stackit log # recent trunk history, stacks collapsed
stackit log v1.4.0..main # a revision range
stackit log --since=... # great for changelogs
stackit log --json # stable feed for release tooling
stackit log -n 20 # limit entries

What you need to do

Mostly retrain one finger:

• Reach for stackit tree (or stackit t) where you used to type stackit log.
• Update any scripts, aliases, or muscle memory that called stackit log for the branch graph.
• Reinstall the stackit skills