Skip to content

🙈 [git] cp gitignore from template-repo - #36

Merged
chicks-net merged 1 commit into
mainfrom
chicks/2026-09-21-cp-gitignore
Sep 21, 2026
Merged

chicks-net merged 1 commit into
mainfrom
chicks/2026-09-21-cp-gitignore

Conversation

@chicks-net

Copy link
Copy Markdown
Member

Done

  • 🙈 [git] cp gitignore from template-repo

Meta

(Automated in .just/gh-process.just.)

Signed-off-by: Christopher Hicks <chicks.net@gmail.com>
@claude

claude Bot commented Sep 21, 2026

Copy link
Copy Markdown

Review

Small, low-risk change — a new .gitignore copied from the org's template repo. This satisfies the .gitignore requirement in just compliance_check, so it's a welcome addition.

Code quality / correctness

  • No issues. It's a static config file, nothing to break.
  • Including .env in the deny list is a good default — helps prevent accidental secret commits.
  • .claude/settings.local.json.backup and /.opencode/* entries are sensible for keeping local tool state out of the repo.

Minor nitpick (non-blocking)

  • A chunk of this file is Go-specific (*.exe, *.dll, *.so, go.work, go.work.sum, the link to the Go allow-list template). Per this repo's own CLAUDE.md, it's a meta-repo of GitHub Issues with no application code, so those entries won't do anything here. Since it's copied verbatim from template-repo for consistency across the org, that's probably intentional boilerplate rather than a mistake — just flagging in case the Go-specific bits were meant to be trimmed for this particular repo.

Performance / security / test coverage

  • N/A — non-code config file, nothing to test, no security surface beyond the (positive) .env exclusion.

Overall: LGTM, fine to merge as-is.

@chicks-net
chicks-net merged commit 64a41ae into main Sep 21, 2026
2 checks passed
@chicks-net
chicks-net deleted the chicks/2026-09-21-cp-gitignore branch September 21, 2026 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant