Implement worktree support for traverse command

[PawelLipski]

Based on PR #1528

Chain of upstream PRs as of 2025-11-14

• PR Rename worktree-related methods in GitClient #1528:
  develop ← refactor/rename-worktree-git-ops

  • PR Implement worktree support for traverse command #1524 (THIS ONE):
    refactor/rename-worktree-git-ops ← improve/1522-worktree-switch-traverse

• Add get_worktrees() and get_worktree_path() methods to GitOperations
• Modify traverse to cd into worktrees where branches are checked out
• Cache worktree information to avoid repeated git worktree list calls
• Add informative messages when changing directories to worktrees
• Add comprehensive tests for worktree handling including detached HEAD cases
• Add integration test for traverse with multiple worktrees

Fixes #1522

TBD: how about checkout from other commands like git machete go? ➡️ leave as is, there's no easy way to switch shell's wd from inside Python process; just fail

TODO: mention in docs ➡️ done

[codecov-commenter]

Codecov Report

❌ Patch coverage is 98.64865% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 98.61%. Comparing base (a4f4137) to head (64f2b56).

Files with missing lines	Patch %	Lines
git_machete/git_operations.py	97.56%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@                         Coverage Diff                          @@
##           refactor/rename-worktree-git-ops    #1524      +/-   ##
====================================================================
- Coverage                             98.62%   98.61%   -0.01%     
====================================================================
  Files                                    26       26              
  Lines                                  4278     4344      +66     
  Branches                                812      828      +16     
====================================================================
+ Hits                                   4219     4284      +65     
  Misses                                   38       38              
- Partials                                 21       22       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[lsierant]

@PawelLipski I've tested it locally and works flawlessly! Thanks!

The only thing (which I'm not sure it should addressed) is a slight UX/flow difference when the branch in a worktree is dirty and cannot be manipulated (e.g. rebased).

Without the worktree, after something fails when traversing, git-machete leaves the current tree in the currently processing branch, so it's easy to fix it and proceed with another traverse.

With worktrees, it cd into a worktree but when it exists with an error, you're still in the current worktree. Slightly annoying, but not blocking!

Worth considering having this UX unified.

[PawelLipski]

With worktrees, it cd into a worktree but when it exists with an error, you're still in the current worktree. Slightly annoying, but not blocking!

Yeah, I think it's going to be hard to work around, that's more of an OS limitation (Linux/macOS/Windows) — a process can't change its parent's working directory (Reddit).

I'll instead make traverse print a warning (as the last thing in the output) which encourages the user to cd to the worktree corresponding to the checked out branch. The warning will be always printed if the initial WD doesn't correspond to the checked out branch, regardless of whether traverse failed or finished successfully.