See what a .dockerignore change actually includes or excludes.
Compare two policies against the same local tree. Get added and removed files, byte impact, and the matching rule on each side. Use readable output for review or deterministic JSON and exit-code gates in CI.
One Go binary. Official Moby matching. No Docker daemon or file uploads.
Binary candidates, no Go required · Release verification
go install github.com/agent-axiom/ignoreimpact/cmd/ignoreimpact@latestFrom a checkout:
go run ./cmd/ignoreimpact compare \
--context examples/demo/context \
--before examples/demo/before.dockerignore \
--after examples/demo/after.dockerignoreAdded: 1 entries | 18 B
Removed: 1 entries | 11 B
The demo includes node_modules/cache.bin and excludes .env.example: +7 B.
Each changed path also shows its before/after rule. Full JSON output →
Reproduce the 28-second terminal demo.
- Usage: commands, policy selection, JSON, and CI gates
- CI adoption · Reproducible public case studies
- Semantics: matching rules and byte accounting
- Limits: filesystem safety, resource bounds, and scope
- Architecture: code map, contracts, and tests
- Agent guide: working on this repository
- Contributing · Security · MIT license
Bytes describe local regular-file sizes. Image size, actual build transfer, and secret detection are outside the tool's scope. See limits.