2026-10-17 — A file under a nested .gitattributes is never generated (facilitator-on-delegation, drain-many-accounts step 11, refines dcn-2610170652464473): generated files are declared in the root .gitattributes of origin's default branch alone, and since a nested .gitattributes could unset the attribute below it, every file at or below a directory holding one is left out of the generated set, found from the same file listing with no extra git read (iss-2610152125101468).

Frontmatter

.abcd/work/decisions/dcn-2610170749120734-a-file-under-a-nested-gitattributes-is.md
open on GitHub ↗ · commit history ↗

mentions2

• dcn-26101706524644732026-10-17 — Generated files are read from one shared declaration (facilitator-on-delegation, drain-many-accounts step 11, refines dcn-2610161040385152): the files origin's default branch, as last fetched, marks linguist-generated in its root .gitattributes, read as stored from disk with a 256 KiB cap and never fetched; nested .gitattributes files, .git/info/attributes and the working tree are not read, because the declaration must be one every account shares (iss-2610152125101468).
• iss-2610152125101468A reservation footprint can hold a whole directory (docs, hooks, internal/surface/cli), and the overlap check then refuses every other reservation naming any file inside it. Generated files that every verb-adding branch regenerates, such as docs/reference/cli/commands.md, sit inside such directories, so two unrelated intents held by the same person from two copies could not both declare an honest footprint: on 2026-10-15 the messaging reservation's renewal was refused twice and had to leave out .githooks/pre-push, the ruleset mirror and the generated CLI reference, which it does change.