test(security): rebuild local env exclusion on live develop

[seonghobae]

Rebuilds issue #213 from exact protected develop@ae4efe6b2c65fb6353bb81ace618bb03c42d3081 without rewriting stale Draft #214.

This replacement is intentionally test-only RED at exact head 5d5e38b9583c2b669ccfc9db016db8970e94a224. It changes only RepositorySecretFilePolicyTest and reaches the real root .gitignore policy boundary. Protected source currently lacks .env, .env.*, and !.env.example, so hosted RED must be the focused repository-policy assertion after normal compilation/test startup; setup/import/path/fixture failure does not qualify.

After valid RED, apply the smallest Git exclusion GREEN. Then extend the test first to the independent Docker build-context boundary and require the same exclusion rules in .dockerignore before applying that second production correction. Preserve the old #214 two-stage RED→GREEN history only after re-proving it on this live ancestry.

Keep Draft. No old #214 checks/reviews transfer. This slice does not create a secret/template, alter credentials, suppress scanning, change Compose, touch POM/coverage authority, or race canonical docs. Merge remains separately gated by exact-source evidence, complete security/dependency materialization, non-vacuous applicable owned-production coverage, zero valid unresolved findings, and qualifying independent non-author approval.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 113021b9-39a8-4f63-8d5a-80598616850c

📥 Commits

Reviewing files that changed from the base of the PR and between ae4efe6 and 960f3ba.

📒 Files selected for processing (3)

• .dockerignore
• .gitignore
• etl-service/src/test/java/com/xtrmetl/etl/config/RepositorySecretFilePolicyTest.java

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}