Advice on per-worktree private gitignore?
2 messages between Apr 23, 2026 and Apr 23, 2026, from D. Ben Knoble, brian m. carlson.
Plain Markdown or JSON for tools and agents.
Today we have $GIT_DIR/info/exclude for the main worktree, but $(git rev-parse --git-dir)/info/exclude for secondary worktrees does not actually contribute to ignore specs.
Is this a "we never got around to implementing that", an intentional omission, or something else? Since --git-dir is described as parsing $GIT_DIR, I would naturally combine that with the gitignore(1) manual to think that the worktree.git/info/exclude should work.
(Currently it seems that main-worktree/.git/info/exclude applies to all worktrees, which may not be desirable in some circumstances.)
Thanks,
--
D. Ben Knoble
Re: Advice on per-worktree private gitignore?
On 2026-04-23 at 21:26:05, D. Ben Knoble wrote:
Show 11 quoted lines
> Today we have $GIT_DIR/info/exclude for the main worktree, but $(git
> rev-parse --git-dir)/info/exclude for secondary worktrees does not
> actually contribute to ignore specs.
>
> Is this a "we never got around to implementing that", an intentional
> omission, or something else? Since --git-dir is described as parsing
> $GIT_DIR, I would naturally combine that with the gitignore(1) manual
> to think that the worktree.git/info/exclude should work.
>
> (Currently it seems that main-worktree/.git/info/exclude applies to
> all worktrees, which may not be desirable in some circumstances.)
I'm not aware of it being an intentional omission. I think what you want might be useful in some circumstances, but there also might be circumstances where it's not wanted and the user might want the settings in the main worktree to be used everywhere.
So I'd say that we could add it as an optional extension, like `extensions.worktreeConfig`.
--
brian m. carlson (they/them)
Toronto, Ontario, CA