You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,10 @@ It captures practical rules that prevent avoidable CI and PR churn.
13
13
- Tests should verify observable behavior changes, not only internal/config state.
14
14
- Example: for a security option, assert a real secure/insecure behavior difference.
15
15
- Test-only helper files under `src` (for example `*-test-utils.ts`) must be explicitly excluded from package `tsconfig.build.json` so they are not emitted into `build` and accidentally published.
16
+
- Vitest runs tests concurrently by default (`sequence.concurrent: true` in `vitest.config.ts`).
17
+
- Tests that rely on shared/global mocks (for example `vi.spyOn` on shared loggers/singletons) can be flaky due to interleaving or automatic mock resets.
18
+
- Prefer asserting observable behavior instead of shared global mock state when possible.
19
+
- If a test must depend on shared/global mock state, use `it.sequential(...)` or `describe.sequential(...)`.
16
20
17
21
## Permission and Escalation
18
22
@@ -30,16 +34,17 @@ It captures practical rules that prevent avoidable CI and PR churn.
30
34
2. Create a branch prefixed with `codex/`.
31
35
3. Implement scoped changes only.
32
36
4. Run required checks: `npm run format`, `npm run lint`, and targeted tests.
33
-
5. Verify git diff only contains intended files. If changes are still being discussed, share the diff and get user approval before committing or pushing.
34
-
6.Commit with focused message(s), using `git commit --no-verify`.
35
-
7.Push branch. Ask for explicit user permission before any force push.
36
-
8.Open PR against `main` using a human-readable title (no `feat(...)` / `fix(...)` prefixes).
37
-
9.Before posting any comment on GitHub issues or PRs, share the proposed message with the user and get explicit approval.
37
+
5. Verify git diff only contains intended files.
38
+
6.Never commit, push, or post on GitHub (issues, PRs, or comments) without first sharing the proposed diff/message and getting explicit user approval.
39
+
7.Commit with focused message(s), using `git commit --no-verify`.
40
+
8.Push branch. Ask for explicit user permission before any force push.
41
+
9.Open PR against `main` using a human-readable title (no `feat(...)` / `fix(...)` prefixes).
38
42
10. Add labels for both change type and semantic version impact.
39
43
11. Ensure PR body includes:
40
44
- summary of changes
41
45
- verification commands run
42
46
- test results summary
47
+
- if semver impact is not `major`, evidence that the change is not breaking
`withWaitStrategy` expects **container names**, not service names. With Docker Compose v2, the default container name for the first replica is usually `<service>-1`.
Interact with the containers in your compose environment as you would any other Generic Container. Note that the container name suffix has changed from `_` to `-` between docker-compose v1 and v2 respectively.
192
+
Interact with the containers in your compose environment as you would any other Generic Container. Compose-managed container names use the `<service-name>-<index>` format.
Copy file name to clipboardExpand all lines: packages/testcontainers/fixtures/docker/docker-with-dockerignore-nested-exclusions/example4/nested/example4.txt
0 commit comments