Fix Google's Antigravity support

[ivanviragine]

Pull Request

Description

Fix issue where it is not opening in the right worktree directory anymore (needs . when calling).

Motivation

Fix issue.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code refactoring (no functional changes)
• Other (please describe):

Testing

Manual Testing Checklist

Tested on:

• macOS
• Linux (specify distro: ______)
• Windows (Git Bash)

Core functionality tested:

• git gtr new <branch> - Create worktree
• git gtr go <branch> - Navigate to worktree
• git gtr editor <branch> - Open in editor (if applicable)
• git gtr ai <branch> - Start AI tool (if applicable)
• git gtr rm <branch> - Remove worktree
• git gtr list - List worktrees
• git gtr config - Configuration commands (if applicable)
• Other commands affected by this change: git gtr adapter, git gtr help editor

Test Steps

1. Run existing BATS test suite: all 236/236 tests pass with no regressions
2. Run git gtr adapter and verify antigravity appears in the editor list
3. Run git gtr help editor and verify antigravity is listed among available editors
4. Run ./scripts/generate-completions.sh --check and verify completions are in sync
5. Verify fish completion for gtr.ui.color now shows "Color output mode (auto, always, never)" description

Expected behavior: Antigravity appears as a built-in editor option in all help, adapter, completion, and configuration surfaces. Fish completion for gtr.ui.color shows the correct description.

Actual behavior: Matches expected behavior.

Breaking Changes

• This PR introduces breaking changes
• I have discussed this in an issue first
• Migration guide is included in documentation

Checklist

Before submitting this PR, please check:

• I have read CONTRIBUTING.md
• My code follows the project's style guidelines
• I have performed manual testing on at least one platform
• I have updated documentation (README.md, CLAUDE.md, etc.) if needed
• My changes work on multiple platforms (or I've noted platform-specific behavior)
• I have added/updated shell completions (if adding new commands or flags)
• I have tested with both git gtr (production) and ./bin/gtr (development)
• No new external dependencies are introduced (Bash + git only)
• All existing functionality still works

Additional Context

Files changed:

• lib/adapters.sh — Added _EDITOR_DOT to denote need for adding . when opening the editor

---

License Acknowledgment

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache License 2.0.

Summary by CodeRabbit

• New Features

  • Introduced a new dot mode modifier for editor adapters, enabling editors to launch with the current directory represented as "." instead of the full file path for more flexible path handling.

• Tests

  • Added test coverage validating proper parsing and behavior of the new dot mode modifier.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

This change introduces a new "dot" editor adapter mode that launches editors with the current directory represented as "." instead of full paths. The _EDITOR_DOT flag controls this behavior, is parsed from registry entries, and a test case validates the functionality.

Changes

Cohort / File(s)	Summary
Editor Adapter Enhancement lib/adapters.sh	Adds new _EDITOR_DOT flag to editor adapter system. Registry entries updated to include dot modifier (notably for antigravity). Editor loading logic now checks dot flag and changes directory to target path with "." when workspace is not provided.
Test Coverage tests/adapters.bats	New test case validates that antigravity editor entry correctly parses both workspace and dot flags, setting both to 1 after registry load.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A dot mode now blooms in the editor's domain,
Where "." replaces paths like drops in the rain,
The registry parsed with newfound delight,
Our antigravity soars to new heights! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding support for the dot flag to fix Antigravity editor behavior to open in the correct worktree directory.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}