From 45c0f997b7c8f90984b7b646589092fab41b59cb Mon Sep 17 00:00:00 2001 From: clawbot <35+clawbot@noreply.example.org> Date: Mon, 16 Nov 2026 23:34:37 +0000 Subject: [PATCH] REPO_POLICIES: Git and secrets 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 --- prompts/REPO_POLICIES.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/prompts/REPO_POLICIES.md b/prompts/REPO_POLICIES.md index 7b4dc4f..cb2fd11 100644 --- a/prompts/REPO_POLICIES.md +++ b/prompts/REPO_POLICIES.md @@ -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`