Skip to content

chore(cli): stop leaving e2e scratch as untracked "fixtures" #662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
beyondnetPeru merged 1 commit into from
Aug 23, 2026
Merged

chore(cli): stop leaving e2e scratch as untracked "fixtures" #662

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions src/sdk/cli/.gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,19 @@ coverage/
AGENTS.md
MASTER_INDEX.md

# E2E scratch trees. Despite the name, NOTHING under test/fixtures/ is authored:
# every directory in it (drift-repo, test-repo, empty-repo, arch-repo, sdlc-core,
# parity-test) is built by an `fs.ensureDir` in the e2e that uses it, and most are
# removed again in `afterAll`. They survive only when a run is interrupted before
# its teardown — which then leaves generated YAML and drift-history JSON showing as
# untracked forever, inviting a `git add -A` to fossilise them as if they were
# checked-in samples.
#
# If a REAL committed fixture is ever needed, put it somewhere else — the tracked
# ones live in src/sdk/cli/test-project/ — or force-add it deliberately. An
# authored file dropped in here would be ignored silently.
test/fixtures/

# Jest cache
.jest-cache/

Expand Down
Loading