Add support for worktrees #45
Replies: 2 comments 5 replies
-
|
I'm leery of this idea of coupling worktrees to (transient) branches. One reason is that IIRC, it can be difficult to delete worktrees that contain Git submodules (and my repos often do). Additionally, transient worktrees will create clutter in the recent list in IDEs, and I imagine there would be extra disk/processing churn from features like Intellisense. Due to considerations like these, my worktrees are long lived, named like Food for thought. |
Beta Was this translation helpful? Give feedback.
-
|
To my understanding workfree is and alternative to Gitflow. It is way git decided to implement same functionality. So to mee it is either Git Flow or may be even same flow but through Worktrees. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Extend topic branch workflows to support Git worktrees. When creating a topic branch, users can optionally create a corresponding worktree, enabling parallel development and simplifying AI-assisted or automated workflows where changes can be merged back once completed.
This feature includes:
~/Dev/git-flow-next-worktrees/{branch})By integrating worktrees directly into the branch lifecycle, developers can work on multiple features simultaneously without frequent context switching or repository duplication.
Beta Was this translation helpful? Give feedback.
All reactions