feat: move env seeding onto envFiles#6
Merged
Merged
Conversation
pkudinov
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
seedEnvFileswithenvFiles[].seedFromso seeding and patching live on the same env-file entry.envFiles[].patchesoptional, defaulting to an empty array for seed-only env files.wtskill, config tests, env command tests, and env patcher tests for the new API.Validation
pnpm testpnpm buildpnpm lintenvFiles: [{ source: ".env", seedFrom: ".env.example" }]with omittedpatches, verifying developer values are preserved and missing vars are appended.