mirror of
https://github.com/bilawalsidhu/gods-eye-view.git
synced 2026-11-04 10:24:02 +00:00
`--write` wrote CHANGELOG.md and then removed fragments one by one, so a failure after the write left surviving fragments that a rerun spliced in a second time. The write is now staged. The assembled file goes into changelog.d/.assembling/, the fragments are renamed in beside it, and renaming the assembled file over CHANGELOG.md is the single commit point. A run that fails rolls itself back when it can; otherwise the next `npm run changelog` reads the staging directory and either restores the fragments (assembled file still staged) or deletes the leftovers (batch landed). `--check` reports a staged batch instead of reporting past it. A failure-injection test makes every filesystem call in a `--write` fail in turn, both as a one-off error and as a crash with no in-process rollback. It asserts the retry produces exactly the uninterrupted CHANGELOG.md, with each entry once and an empty directory. The test fails against the previous write-then-delete and against delete-first. Co-Authored-By: Claude Opus 5.5 <[email protected]>
27 lines
744 B
Plaintext
27 lines
744 B
Plaintext
node_modules
|
|
dist
|
|
# Credential files. `.env` alone is not enough: Vite's loadEnv (see
|
|
# server/standalone/vite.config.js) and scripts/setup-doctor.mjs both read the
|
|
# full dotenv ladder — .env, .env.local, .env.<mode> and .env.<mode>.local —
|
|
# so a key placed in any of them is live for the app. Only .env was ignored,
|
|
# leaving the other three committable. .env.example is the tracked template.
|
|
.env
|
|
.env.*
|
|
!.env.example
|
|
*.log
|
|
screenshots/
|
|
qa-shots/
|
|
output/
|
|
.gev-logs/
|
|
.gev-cache/
|
|
# Browser QA gate evidence (screenshots, console and network dumps).
|
|
qa-artifacts/
|
|
.DS_Store
|
|
.gstack/
|
|
3d-models/
|
|
pinokio/ENVIRONMENT
|
|
pinokio/.installed
|
|
|
|
# Transient: a release interrupted mid-assembly (npm run changelog recovers it)
|
|
changelog.d/.assembling/
|