Skip to content

v1.1.0

Choose a tag to compare

View all tags
@asatamax asatamax released this 19 Jul 05:08
· 7 commits to main since this release
v1.1.0
3b0950a

What's Changed

Explicit path argument now overrides configured roots file

Previously, when a roots file auto-resolved (via $GIT_FLEET_ROOTS, ~/.config/git-fleet/roots, or ~/.git-fleet-roots), an explicit PATH argument was silently ignored and multi-root mode ran instead — contradicting the README examples.

Now every command resolves its target in this order:

  1. --roots FILE given explicitly → multi-root mode using that file
  2. PATH argument given explicitly → single-root ad-hoc scan of that path (auto-resolution skipped entirely)
  3. Auto-resolved roots file → multi-root mode
  4. Otherwise → single-root scan of the current directory
# Even with a roots file configured, an explicit path scans only that tree
git-fleet status ~/Development/oss

# Ad-hoc scan of the current directory
git-fleet status .

Passing PATH together with --roots is now an error (exit code 1).

Applies uniformly to all 9 commands (status, diff, fetch, pull, push, sync, list, who, remote). The MCP tool schema (--schema) documents the new precedence in a resolutionPrecedence block.

Full Changelog: v1.0.9...v1.1.0

Assets 2
Loading