From 71e80bcc8fdac116718f84aeb9c206947047bec8 Mon Sep 17 00:00:00 2001 From: Chemaclass Date: Fri, 14 Aug 2026 06:23:45 +0200 Subject: [PATCH] docs(quickstart): describe what init now does to .env #1176 made init idempotent: when .env already points BASHUNIT_BOOTSTRAP at the same file it says so and changes nothing, and only a differing value is commented out and replaced. The changelog recorded that; this page still described the old unconditional comment-and-append. Found by following the quickstart literally, as a new user would. Every other step -- init, the manual test file, ./lib/bashunit tests, the default path, --filter and --parallel -- behaves exactly as written, including the sample output. --- docs/quickstart.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/quickstart.md b/docs/quickstart.md index 8bc11ce0..ae7352a4 100644 --- a/docs/quickstart.md +++ b/docs/quickstart.md @@ -51,8 +51,9 @@ It creates, in the current directory: - `.github/workflows/tests.yml` — a CI workflow using the official action - `.env` — with `BASHUNIT_BOOTSTRAP=tests/bootstrap.sh`, which is what makes the bootstrap load -If `.env` already sets `BASHUNIT_BOOTSTRAP`, `init` comments that line out and appends the -new one, so check the diff before committing. +If `.env` already sets `BASHUNIT_BOOTSTRAP` to that same file, `init` leaves it alone and +says so, so re-running is safe. If it points somewhere else, the old line is commented out +and the new one appended — check the diff before committing. Alternatively, create your tests manually: