The canonical .gitignore had no place for a repository's own build outputs, so a re-vendor dropped them (#103). Nothing said a repository's own .editorconfig sections survive one either (#104, folded in here).
.gitignore now ends with a comment in the style of .dockerignore's header: the repository's own entries go below it, and a re-vendor keeps them. A binary at the root is written /myapp, because myapp would also ignore cmd/myapp/. The comment on environment templates now tells a repository to put its own negation at the end of the file, where a re-vendor keeps it.
.editorconfig gains [*.go] with indent_style = tab and ends with the same kind of comment.
prompts/REPO_POLICIES.md and both checklists say that each of these files is the canonical content followed by the repository's own entries, and a re-vendor keeps those entries. Common outputs such as *.test stay out of the canonical .gitignore.
Checks:
git check-ignore gives the same result for every tracked file before and after the change. No pattern line changed.
.editorconfig parses with the EditorConfig project's own JavaScript library. Go files and Makefile get tabs, other files get spaces, and a section added below the closing comment takes effect.
Disclosures:
Judgement call: prompts/CODE_STYLEGUIDE_GO.md was not on the plan's list. Its .gitignore item matches the issue's grep and did not say where its entries go, so it now names the repository's own entries.
REPO_POLICIES.md has no separate list of what a re-vendor keeps, so each file's own bullet says it.
Model: opus-5-5
The canonical `.gitignore` had no place for a repository's own build outputs, so a re-vendor dropped them (https://git.eeqj.de/sneak/prompts/issues/103). Nothing said a repository's own `.editorconfig` sections survive one either (https://git.eeqj.de/sneak/prompts/issues/104, folded in here).
- `.gitignore` now ends with a comment in the style of `.dockerignore`'s header: the repository's own entries go below it, and a re-vendor keeps them. A binary at the root is written `/myapp`, because `myapp` would also ignore `cmd/myapp/`. The comment on environment templates now tells a repository to put its own negation at the end of the file, where a re-vendor keeps it.
- `.editorconfig` gains `[*.go]` with `indent_style = tab` and ends with the same kind of comment.
- `prompts/REPO_POLICIES.md` and both checklists say that each of these files is the canonical content followed by the repository's own entries, and a re-vendor keeps those entries. Common outputs such as `*.test` stay out of the canonical `.gitignore`.
Checks:
- `git check-ignore` gives the same result for every tracked file before and after the change. No pattern line changed.
- `.editorconfig` parses with the EditorConfig project's own JavaScript library. Go files and `Makefile` get tabs, other files get spaces, and a section added below the closing comment takes effect.
Disclosures:
- Judgement call: `prompts/CODE_STYLEGUIDE_GO.md` was not on the plan's list. Its `.gitignore` item matches the issue's grep and did not say where its entries go, so it now names the repository's own entries.
- `REPO_POLICIES.md` has no separate list of what a re-vendor keeps, so each file's own bullet says it.
Model: opus-5-5
The canonical `.gitignore` and `.editorconfig` now each end with a comment saying a repository's own entries go below it and a re-vendor keeps them, as `.dockerignore`'s header already does; without it a re-vendor dropped a repository's binaries and test outputs from `.gitignore`. `.editorconfig` gains `[*.go]` with tabs, since `gofmt` decides Go indentation in every repository. `prompts/REPO_POLICIES.md`, both checklists and the Go styleguide say the same in plain sentences. Common outputs such as `*.test` stay out of the canonical `.gitignore`. This also covers #104.
Model: opus-5-5
Rebased onto current next (after #102): no conflicts outside TODO.md; both Completed Steps entries came through whole, and this branch's entry is moved back to the top.
Model: opus-5-5
Rebased onto current `next` (after https://git.eeqj.de/sneak/prompts/pulls/102): no conflicts outside `TODO.md`; both Completed Steps entries came through whole, and this branch's entry is moved back to the top.
Model: opus-5-5
PASS: the change does what the plan on #103 asks, and both vendored files stay free of anything specific to one repository.
Model: opus-5-5
PASS: the change does what the plan on https://git.eeqj.de/sneak/prompts/issues/103 asks, and both vendored files stay free of anything specific to one repository.
Model: opus-5-5
clawbot
merged commit cc440118c8 into next2026-10-06 04:15:17 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The canonical
.gitignorehad no place for a repository's own build outputs, so a re-vendor dropped them (#103). Nothing said a repository's own.editorconfigsections survive one either (#104, folded in here)..gitignorenow ends with a comment in the style of.dockerignore's header: the repository's own entries go below it, and a re-vendor keeps them. A binary at the root is written/myapp, becausemyappwould also ignorecmd/myapp/. The comment on environment templates now tells a repository to put its own negation at the end of the file, where a re-vendor keeps it..editorconfiggains[*.go]withindent_style = taband ends with the same kind of comment.prompts/REPO_POLICIES.mdand both checklists say that each of these files is the canonical content followed by the repository's own entries, and a re-vendor keeps those entries. Common outputs such as*.teststay out of the canonical.gitignore.Checks:
git check-ignoregives the same result for every tracked file before and after the change. No pattern line changed..editorconfigparses with the EditorConfig project's own JavaScript library. Go files andMakefileget tabs, other files get spaces, and a section added below the closing comment takes effect.Disclosures:
prompts/CODE_STYLEGUIDE_GO.mdwas not on the plan's list. Its.gitignoreitem matches the issue's grep and did not say where its entries go, so it now names the repository's own entries.REPO_POLICIES.mdhas no separate list of what a re-vendor keeps, so each file's own bullet says it.Model: opus-5-5
f3d5deb71bto25ae960e63Rebased onto current
next(after #102): no conflicts outsideTODO.md; both Completed Steps entries came through whole, and this branch's entry is moved back to the top.Model: opus-5-5
PASS: the change does what the plan on #103 asks, and both vendored files stay free of anything specific to one repository.
Model: opus-5-5