ci: exempt env templates from danger env protection rule

[LucasSantana-Dev]

Summary

PR #1674 (external contributor) fails danger with no possible resolution: the .env* protection rule fires on .env.example, and its own message demands "explicit confirmation per project policy" but the code offers no confirmation mechanism. Any PR touching the tracked template fails forever.

Fix: exempt the standard template names (.env.example, .env.sample, .env.template) from the fail. Real .env files still fail.

Danger runs on pull_request_target against base-repo code, so once this merges, re-running danger on #1674 picks it up without a branch update.

Test plan

• danger re-run on fix(docker): make compose stack boot from a fresh .env #1674 passes (only the changelog warning remains)

---

Summary by cubic

Exempts .env.example, .env.sample, and .env.template from the Danger .env* protection so template updates don’t fail CI, while still blocking real .env files. This unblocks PRs that touch tracked env templates (e.g., #1674).

• Bug Fixes
  • Updated dangerfile.ts to ignore standard env templates in the .env* check.
  • The rule still fails on actual .env files.
  • Re-running Danger on affected PRs will pass.

^{Written for commit 0520fe5. Summary will update on new commits.}

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 33 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5e7f5239-90b7-4f7a-84f9-3ca5b3239951

📥 Commits

Reviewing files that changed from the base of the PR and between a424106 and 0520fe5.

📒 Files selected for processing (1)

• dangerfile.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/danger-env-template-exemption

---

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.}

[github-actions]

Failed to generate code suggestions for PR

[cubic-dev-ai]

No issues found across 1 file

<sub>Auto-approved: This fix exempts tracked env templates from a CI protection rule that was incorrectly blocking them, while preserving the fail on real .env files. The change is narrow, clearly beneficial, and carries no operational or security tradeoff.

Re-trigger cubic</sub>

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud