Restore connections.env without triggering post-checkout hooks
git checkout fires post-checkout even for a single-file checkout (flag=0), which was tripping an rsync hook in the target repo. Read the committed blob with git cat-file instead and write it directly - plumbing, no worktree update, no hooks - with a test that plants a post-checkout hook and asserts it never runs.
This commit is contained in:
@@ -56,7 +56,7 @@ dev_tools foo down
|
||||
## What it does
|
||||
|
||||
1. Starts or stops the Docker Compose service defined by `DOCKER_SERVICE` / `DOCKER_DIR`.
|
||||
2. `conf/global/connections.env`: `up` toggles it to the CI credentials and marks it `git update-index --assume-unchanged` to avoid accidental commits; `down` unmarks it and restores it to its committed state with `git checkout` (rather than computing the reverse toggle), so it's guaranteed byte-for-byte identical to HEAD.
|
||||
2. `conf/global/connections.env`: `up` toggles it to the CI credentials and marks it `git update-index --assume-unchanged` to avoid accidental commits; `down` unmarks it and restores it to its committed state by reading the committed blob with `git cat-file` (rather than computing the reverse toggle or running `git checkout`, which would fire the repo's `post-checkout` hook), so it's guaranteed byte-for-byte identical to HEAD.
|
||||
3. Toggles database connection entries in `<PROJECT_DIR>/conf/local/.env`: `up` switches the connection to `ci`, `down` switches it to `staging`.
|
||||
|
||||
## Tests
|
||||
|
||||
Reference in New Issue
Block a user