feat: implement intelligent merge behavior for .env synchronization #12
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
Fixes #6 - Changes the behavior from overwriting
.envfiles to intelligently merging them.What Changed
.env.examplenow update existing keys in.envwhile preserving keys that aren't in the examplelib/readEnv.jsparses existing.envfiles for mergingBehavior
.envexists: merges with.env.example, preserving custom keys.envdoesn't exist: creates new file (original behavior).env.examplekeys appear first, followed by preserved keys from existing.envTest Plan
readEnvfunction.env.example.env.example.envif it doesn't exist.envfiles🤖 Generated with Claude Code