Re: [PATCH v2 0/3] Ensure unique worktree ids across repositories
- From
Caleb White <cdwhite3@pm.me>
- Date
- Nov 30, 2024, 16:08 UTC
- Message-ID
- <D5ZN60S3JMS8.UXLUSM5IOFCX@pm.me>
- In-Reply-To
- <00c901db42c0$38f95520$aaebff60$@nexbridge.com>
On Fri Nov 29, 2024 at 6:38 PM CST, rsbecker wrote:
Show 15 quoted lines
> On November 29, 2024 7:09 PM, Caleb White wrote: >>If the `develop` directory is deleted, cleanup detection is handled by the `git >>worktree prune` command, which will remove worktrees under `.git/worktrees/*` >>that are no longer valid. This happens automatically after the expiry time or it can be >>executed manually. Of course, executing `git worktree remove develop` will also >>remove the worktree and its associated worktree id. > > This last bit is an assumption, and not necessarily valid. Scripts that use worktrees > may maintain lists or their own pointers. It is important to be able to emulate > cleanup functions - something I discovered early in the worktree functions > when released. I need to make sure that cleanup will continue to have enough > information - prior to git worktree cleanup - to function correctly. This will > need coordination with people who have such scripts in my community. It > probably will not impact you, but I would have appreciated more than one > release notice on this capability.
I'm not sure I understand the specific use-case you're talking about. Could you provide an example?
However, I suppose I can add a config / env variable to be able to disable this new functionality.
Best,
Caleb