Repository navigation
fix(config): keep project dotenv loading inside the working directory - #1775
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Hi! 👋 Join our CodeGraphContext Discord channel to collaborate: https://discord.gg/dR4QY32uYQ |
🔍 PR Code Graph Analysisfix(config): keep project dotenv loading inside the working directory (#1775) 📊 Interactive VisualizationView the blast radius graph: PR Reviewer Dashboard 📦 ArtifactsThe graph JSON has been uploaded as a build artifact: Generated by CodeGraphContext using FalkorDB Lite |
Shashankss1205
left a comment
There was a problem hiding this comment.
Ready to merge. Project dotenv discovery is now cwd-only, preserving .codegraphcontext/.env precedence, context gating, force/ignore flags and environment overrides. 17 focused tests pass. The documented local fast suite passes 1,810 tests with 8 skips; a preliminary proxy-misconfigured run is not counted as a pass. All current-head CI checks pass, including Python 3.12–3.14, platform E2E, strict four-backend parity and packaging/security. The config reference explains the directory boundary and migration.
Starting CGC in a nested project could load an unrelated parent project's .env and override settings in per-repo mode. Resolve only cwd/.codegraphcontext/.env or cwd/.env, preserving that precedence, context-mode gating and explicit environment overrides. Forced project loading retains the same directory boundary.
Closes #1099.
Validation: 17 focused config tests pass, including parent .env/.codegraphcontext exclusion, cwd precedence, force/ignore flags, environment overrides, existing profile isolation and encoding coverage. Updated the configuration reference to explain the boundary and migration to project-root or global settings. No license changes.