Repository navigation
0.8.2 - #38
Merged
Merged
0.8.2#38
Conversation
Worktree colours were the feature the tool leads with, and two of four worktrees came out perceptually identical about one time in five. Both halves of that are fixed: sibling names no longer land on adjacent hues, and colours now vary in lightness and saturation as well. Nothing to reinstall — the shell wrapper is unchanged.
The 0.8.2 notes described the /release skill under Internal. The CHANGELOG ships in the npm package and is read by someone deciding whether to upgrade; how releases get prepared is not their concern. It also contradicted the skill's own step 1b, which says .claude/ never reaches the package and cannot justify a release. Something that cannot justify a release does not belong in the notes for one. Internal is now scoped to what a reader could notice from outside: a dependency bump that changes the install, a raised Node floor.
Reverses the previous commit on the user's call. The reasoning against still holds — the CHANGELOG ships in the package and .claude/ does not, so a reader who installed git-wtree cannot act on it — but a changelog serves two audiences, and the second is whoever reads this history in six months wondering when the release skill appeared. The skill now says so explicitly rather than banning the section: keep it short, say when something does not ship, and never let it justify a release on its own.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
0.8.2
Nothing to reinstall — the shell wrapper is unchanged.
Fixed
Sibling branches got indistinguishable colours.
feature-aandfeature-blanded 1° apart on the hue wheel — the same colour, to a human —and so did
fix-1/fix-2,pr-101/pr-102, and every other pair differingin a trailing character. The hash advanced by one for an input that advanced
by one, and the low bits went straight into the hue. It now runs through an
avalanche step, so those pairs sit 85–180° apart.
Colours are drawn from four wheels instead of one. Hue alone gives 360
places to stand and branch names land on them at random, so with four
worktrees open two were perceptually identical about one time in five —
the birthday problem rather than any flaw. Lightness and saturation now vary
too, which drops that to roughly one in fourteen. White text stays above
WCAG AA throughout, measured at 4.53:1 in the worst case.
It narrows the odds rather than closing them. Closing them would mean
coordinating colours across worktrees instead of deriving them from a name,
which costs determinism — the same branch would look different on another
machine — and breaks under two concurrent
gwt add, a real scenario whenagents run in parallel. Not worth it for the remaining seven percent; rename
a branch if two ever clash.
After merging
git tag v0.8.2 && git push --tagsCI stages the package; approve it on npmjs.com with 2FA. 162 tests.