REPO_POLICIES: Git and secrets
check / check (push) Canceled after 0s

Only a heading and a comma before "because" in the build-artifact
exception: the reorder already put these five rules together, and
none is cut.

Model: opus-5-5
This commit is contained in:
clawbot committed 2026-11-16 23:34:37 +00:00
1 parent 287ffdf43e
commit 45c0f997b7
1 file changed
+4 -2
+4 -2
View File
@@ -64,6 +64,8 @@ style conventions are in separate documents:
yarn's release file is third-party code, and git pins it. `yarn set version`
writes it to `.yarn/releases/` once, given an exact version.
# Git and secrets
- Never commit secrets. `.env` files, credentials, API keys, and private keys
must be in `.gitignore`. No exceptions.
@@ -82,8 +84,8 @@ style conventions are in separate documents:
The build process (e.g. Dockerfile, Makefile) should generate these at build
time. Notable exception: Go protobuf generated files (`.pb.go`) ARE
committed because repos need to work with `go get`, which downloads code but
does not execute code generation.
committed, because repos need to work with `go get`, which downloads code
but does not execute code generation.
- Every repo with software must have a root `Makefile` with these targets:
- `make bootstrap`