You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(gitignore): ignore all .env* files, keep example templates - #3809
Low Risk .gitignore only; reduces accidental commit of secrets with no runtime or auth behavior changes.
Overview
Adds a catch-all .env* rule at the bottom of .gitignore so variant env files (e.g. .envrc, .env-staging) are ignored even when they do not match the existing .env / .env.* entries.
Immediately after that rule, !.env.example and !.env.*.example are re-applied so safe template files stay tracked and are not swallowed by the broader pattern.
Reviewed by Cursor Bugbot for commit 1bf5d97. Bugbot is set up for automated code reviews on this repo. Configure here.
The existing rules cover .env and .env.*, but not names without the dot
such as .envrc or .env-staging. Those can hold secrets too.
Add a catch-all .env* rule and re-allow the .env.example and
.env.*.example templates after it, so they stay tracked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This change safely ignores environment files while preserving all tracked example templates. No actionable merge-blocking risk remains.
Architecture risk: Low · up to 1bf5d
The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.
Changed systems: None identified.
Architecture concerns
No architecture-level concerns identified.
Review details
Before / after behavior
observed — Modified behavior in .gitignore: Adds a broad .env* ignore pattern and exceptions for .env.example and scoped .env.*.example templates.
Pre-merge checks: 4 · 1
Failed checks: 1 warning
Check name
Status
Explanation
Resolution
Description check
The description explains the change and verification steps, but it omits the required Type of Change, Checklist, and Related Issues sections. It also uses a Verification section instead of the require…
Add the required Type of Change, Test Plan, Checklist, and Related Issues sections. Mark applicable options and state that the change is configuration-only if no application tests were needed. Preserve the existing verification details unde…
Passed checks: 4 passed
Check name
Status
Explanation
Title check
The title clearly and concisely describes the main change: ignoring .env* files while keeping example templates tracked.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Full details: Description check
Explanation
The description explains the change and verification steps, but it omits the required Type of Change, Checklist, and Related Issues sections. It also uses a Verification section instead of the required Test Plan section.
Resolution
Add the required Type of Change, Test Plan, Checklist, and Related Issues sections. Mark applicable options and state that the change is configuration-only if no application tests were needed. Preserve the existing verification details under Test Plan or an equivalent clearly labeled section.
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Reviewing files that changed from the base of the PR and between 77dd495 and 1bf5d97.
Files selected for processing: 1
.gitignore
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 7 remain after this review.
Codex CLI review run by a Claude Code session on the exact head above.
No blocking problems found at 1bf5d973. The .gitignore change matches its claims: git check-ignore confirms the listed environment-file variants are ignored and all five tracked templates remain allowed. No runtime, tenant isolation, or public-copy changes. The description mentions no unresolved bot threads.
Brings in #3780 (relative imports in three ingestion modules plus the
test_no_absolute_app_imports guard), #3793, #3794, #3807 and #3809. Both
conflicts (stripe_billing/rate_limiting.py, webhook_compat.py) were the same
relative-import change made on both sides; main's wording kept. The new
guard test, the WI-02 bare-import guard, the route snapshot test and the
repository gates pass on the merged tree.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GyhDYGPjbfDzVjRUqkvz4B
Brings in #3780 (relative imports in three ingestion modules plus the
test_no_absolute_app_imports guard), #3793, #3794, #3807 and #3809. Both
conflicts (stripe_billing/rate_limiting.py, webhook_compat.py) were the same
relative-import change made on both sides; main's wording kept. The new
guard test, the WI-02 bare-import guard, the route snapshot test and the
repository gates pass on the merged tree.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GyhDYGPjbfDzVjRUqkvz4B
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.env*ignore rule. The existing.envand.env.*rules miss names like.envrcand.env-staging, which can hold secrets..env.exampleand.env.*.exampleafter the new rule, so the templates stay tracked.This came out of the work on #3782 but is unrelated to EDI, so it is separate.
Verification
git check-ignoreconfirms.envrc,.env-staging,.env.prodandfrontend/.envrcare ignored..envtemplates still resolve to the!rules..gitignoreonly, so no app tests or/verifywere run.🤖 Generated with Claude Code
Note
Low Risk
.gitignoreonly; reduces accidental commit of secrets with no runtime or auth behavior changes.Overview
Adds a catch-all
.env*rule at the bottom of.gitignoreso variant env files (e.g..envrc,.env-staging) are ignored even when they do not match the existing.env/.env.*entries.Immediately after that rule,
!.env.exampleand!.env.*.exampleare re-applied so safe template files stay tracked and are not swallowed by the broader pattern.Reviewed by Cursor Bugbot for commit 1bf5d97. Bugbot is set up for automated code reviews on this repo. Configure here.