Compare commits

Author SHA1 Message Date
sneak 4154f56220 Add vendored REPO_POLICIES.md from prompts repo
check / check (push) Successful in 55s
2026-07-07 01:57:08 +02:00
sneak c246bfc455 Adopt scripts-to-rule-them-all: script/ entrypoints, Makefile shims 2026-07-07 01:57:08 +02:00
3 changed files with 1 additions and 26 deletions
-12
View File
@@ -1,12 +0,0 @@
root = true
[*]
indent_style = space
indent_size = 4
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true
[Makefile]
indent_style = tab
-9
View File
@@ -25,15 +25,6 @@ Bring the repo into policy compliance in one commit:
# Completed Steps
- 2026-08-09: `script/test` now runs
`go test -timeout 30s -race -cover ./...` and, on failure, reruns
verbosely and then exits non-zero, so a test that fails once and
passes on the retry can no longer produce a green build (closes #32).
Enabling `-race` showed the suite cannot meet the 20-second policy
budget: `internal/cli` exceeds the 30-second timeout because the
99MB/100MB boundary cases in `secrets_size_test.go` run roughly 10x
slower under race instrumentation. No flags were weakened and no
tests skipped; the conflict is tracked in #52 for a decision.
- 2026-07-07 Adopted scripts-to-rule-them-all: `script/` entrypoints,
Makefile shims, README Entrypoints section
- 2026-03-11: Secure Enclave unlocker for hardware-backed secret
+1 -5
View File
@@ -9,11 +9,7 @@ main() {
# CGO is required (Makefile exports this too)
export CGO_ENABLED=1
go vet ./...
# The rerun is diagnostic only: `exit 1` keeps the script failing
# even if a flaky test passes on the second attempt.
go test -timeout 30s -race -cover ./... || \
{ echo "--- Rerunning with -v for details ---"; \
go test -timeout 30s -race -v ./...; exit 1; }
go test ./... || go test -v ./...
}
main "$@"