Skip to content

refactor(output): downgrade 'no worktree' message to info#887

Merged
max-sixty merged 1 commit intomainfrom
worktree-warn
Jan 27, 2026
Merged

refactor(output): downgrade 'no worktree' message to info#887
max-sixty merged 1 commit intomainfrom
worktree-warn

Conversation

@max-sixty
Copy link
Owner

Summary

  • Downgrades the "No worktree found for branch X" message from warning (▲) to info (○) when removing a branch that has no associated worktree
  • The BranchOnly code path is only reached when the branch exists locally, so this is informational rather than a warning scenario

Test plan

  • Existing snapshot tests updated to reflect the new output format
  • wt hook pre-merge --yes passes

This was written by Claude Code on behalf of max-sixty

When removing a branch that has no associated worktree, the message
'No worktree found for branch X' was shown as a warning (▲). This is
now an info message (○) since the branch exists and removal proceeds
normally.

The BranchOnly code path is only reached when the branch exists locally
(checked at repository_ext.rs:116), so this isn't a 'something doesn't
exist' warning scenario — it's purely informational.

Co-Authored-By: Claude <noreply@anthropic.com>
@max-sixty max-sixty merged commit 6692352 into main Jan 27, 2026
27 of 30 checks passed
@max-sixty max-sixty deleted the worktree-warn branch January 27, 2026 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant