Skip to content

chore(oss): add /canary to .gitignore and create .dockerignore - #103

Merged
mashkovd merged 1 commit into
mainfrom
chore/oss-artifact-hygiene
May 21, 2026
Merged

mashkovd merged 1 commit into
mainfrom
chore/oss-artifact-hygiene

Conversation

@mashkovd

Copy link
Copy Markdown
Member

Summary

  • .gitignore: adds /canary — the integration-test binary directory was untracked and could accumulate leftover binaries
  • .dockerignore: new file — without it `docker build` context included `.git` history, dev binaries, test artifacts, local databases, `.env` files, and docs

Trivial config-only change — no logic modified.

🤖 Generated with Claude Code

.gitignore: add /canary (the integration-test binary built by the canary
workflow is already excluded by the test runner; the directory itself
was untracked but could accumulate leftover binaries and state).

.dockerignore: new file — without it every docker build context
included .git history, dev binaries (/local, /canary), test artifacts,
local databases, .env files, and documentation. Excluding these reduces
build context size and prevents accidental secret/session data from
reaching the builder layer.
@claude

claude Bot commented May 21, 2026 •

Copy link
Copy Markdown

Claude finished @mashkovd's task in 24s —— View job


Config-only change (.gitignore + .dockerignore). No logic, no security surface. .dockerignore entries are appropriate — excludes .git, dev binaries, secrets, local databases, and docs from the build context.

No P1/P2 findings, good to merge.

@mashkovd
mashkovd merged commit c32c57a into main May 21, 2026
6 checks passed
@mashkovd
mashkovd deleted the chore/oss-artifact-hygiene branch May 21, 2026 07:30
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.

2 participants