git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Advice on per-worktree private gitignore?

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Apr 23, 2026, 21:56 UTC
Message-ID
<aeqVpjPSyyvHDLWR@fruit.crustytoothpaste.net>
In-Reply-To
<CALnO6CCXmA+ATT7CuyWkU6P8qmLCCpMi5Ppr1c78s0heznpVyw@mail.gmail.com>
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
Previous: D. Ben Knoble
Message 2 of 2 in “Advice on per-worktree private gitignore?”
  1. D. Ben KnobleApr 23, 2026
  2. brian m. carlsonApr 23, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.