Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion docs/design/feature-profiles/repo-fixture-builder.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Feature Profile: Repo Fixture Builder

Status: draft for supporting lane implementation
Status: initial implementation available in `test/helpers/repo-fixture.js`

Related:

Expand Down
14 changes: 13 additions & 1 deletion docs/design/repo-fixture-strategy.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,9 @@ Overlays answer:

## Preferred API Shape

The exact implementation can evolve, but the intended model is:
The implementation lives in `test/helpers/repo-fixture.js`. The helper exposes
`repoFixture()`, `createRepoFixture()`, reusable base repos, and scenario
overlays.

```js
const repo = await repoFixture()
Expand Down Expand Up @@ -123,6 +125,16 @@ The point is:
- reusable repo shapes
- composable history/state overlays

## Fixture Isolation

Fixture repos must be isolated from the contributor's host Git configuration
where that configuration would make test behavior nondeterministic or slow.

The canonical builder sets local fixture config for test identity, disables
commit and tag signing, disables inherited hooks, disables fsmonitor, and uses
deterministic commit timestamps. This is part of making fixtures hermetic; it is
not a bypass for this repository's real commit hooks.

## Archived Repo Snapshots

Tarballs or archived repos are allowed when:
Expand Down
Loading
Loading