fix(cli): keep bashunit init idempotent in .env - #1176
Merged
Conversation
init commented out any existing BASHUNIT_BOOTSTRAP and appended a fresh one unconditionally, so three runs left three lines with two inert. The scaffolded files are idempotent, so re-running init is otherwise safe and people do it -- only .env grew. Skip the rewrite when the setting already holds the intended value, and report each outcome: .env was the one file init wrote without announcing it, so a review of what init touched would miss it. Replacing a different value still works, which is what the comment-and-append logic exists for. Closes #1175
This was referenced Aug 13, 2026
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.
🤔 Background
Related #1175
bashunit initcomments out any existingBASHUNIT_BOOTSTRAPand appends afresh one — unconditionally, even when the value is unchanged. Three runs:
The scaffolded files are idempotent, so re-running
initis otherwise safe andpeople do it. Only
.envgrew — and it was the one file written without beingannounced.
💡 Changes
.envoutcome (Created/already sets/Updated)bashunit_init_test.sh, which another test depends on by name