About this software
Adds Git worktree operations to JetBrains IDEs, enabling creation, listing, switching, and removal of worktrees through the IDE interface. The plugin integrates worktree commands into menus and tool windows to manage multiple working trees without leaving the IDE.
Available as a commercial third-party subscription through the JetBrains Marketplace, it targets developers who use Git worktrees to work on multiple branches or tasks concurrently.
Purchase
JetBrains 3rd Party Git Worktree
In Stock
Delivery: 1 working day
Loading...
€11.80
Free and without obligation
Do you need more information or looking for another license?
Benefits
- Create worktrees: Create new Git worktrees directly from the IDE interface
- Switch worktrees: Switch between worktrees without leaving the project window
- Open in new window: Open a worktree in a separate IDE window for parallel work
- List and remove worktrees: View existing worktrees and remove unused ones from the UI
- Marketplace subscription: Commercial licenses are managed through the JetBrains Marketplace subscription
Available languages
- English
Support information
- Documentation: Refer to the plugin page and JetBrains help for usage instructions and notes
- Marketplace updates: Plugin updates and versions are delivered through the JetBrains Marketplace
- Issue tracker: Report bugs or feature requests via the vendor link on the plugin marketplace page
- License management: Manage subscriptions and seats through the JetBrains Account and Marketplace console
- Compatibility notes: Check the plugin page for IDE compatibility and version requirements before installing
Frequently asked questions
What is JetBrains 3rd Party Git Worktree?
An integration that exposes Git worktree functionality within JetBrains IDEs, enabling management of multiple working trees attached to a single Git repository from the IDE.
How does it handle multiple working trees in the IDE?
It exposes Git worktree operations such as creating, listing, switching, and removing worktrees through the IDE, allowing concurrent checkouts of different branches.
Will using worktrees affect commits and repository history?
Worktrees share the same repository metadata and history, so commits made from any worktree appear in the same Git history and branch refs, following standard Git behavior.
How should worktrees be cleaned up after use?
Remove unused worktrees using the Git worktree remove command or the IDE's corresponding action, and delete the working directory after ensuring no uncommitted changes remain.