The squash-merge detective
Squash-merged pull requests are found even when they aren’t titled with the branch name, and land under the release that shipped them. Branches whose ticket key shows up in a later squash get a “likely” tag and are never cleaned up by mistake. Also: the push button now wiggles when commits are waiting for origin.
- Squash detection
- “Likely merged” tag
- Retarget any branch
- Changelog into x.y.z
All 20 changes8 added7 changed5 fixed
Added
- Release branches can change the branch they were cut from. Trunks can take a parent, and work branches can target any existing branch.
- Branches falling behind are grouped under their parent branch.
- Azure DevOps pull requests are read to place merged branches under the release that shipped them.
- Branches whose ticket key appears in a later pull request squash are shown with a "likely" tag. They are never deleted or cleaned up as merged.
- The push button wiggles when commits are waiting to go to origin.
- The commit link animates when new commits land.
- An empty state is shown when no pull request provider is connected.
- "Move unreleased changelog into x.y.z" release branch action: renames the
Unreleasedsection ofCHANGELOG.mdto the release's version, dated today, and commits it on the branch before shipping.
Changed
- Open releases are sorted newest version first.
- Branch views are cached per project, and a quick overview shows first when nothing is cached, so reopening a project is faster.
- Squash merge checks are persisted per commit pair, so they are not repeated.
- The terminal panel is hidden by default.
- Light mode accent colors are tuned.
- Section Clean up buttons are now a brush icon in line with the group row.
- Branch tree rows sit on a raised background, and Shipped has a thin separator above it.
Fixed
- Branches squashed by pull requests are now detected, including squashes not titled with the branch name.
- Squashed branches are placed under the release that shipped them.
- Releases shipped by a later patch of their line are marked as shipped.
- Older releases whose branch still exists are now listed.
- Ahead/behind counts are batched per base branch, so they load faster.