From c066ef4464cb2ea199c40213f11175a052558224 Mon Sep 17 00:00:00 2001 From: clawbot Date: Mon, 9 Mar 2026 17:21:41 -0700 Subject: [PATCH] policy: no build artifacts in version control --- prompts/REPO_POLICIES.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/prompts/REPO_POLICIES.md b/prompts/REPO_POLICIES.md index a0abedf..8478553 100644 --- a/prompts/REPO_POLICIES.md +++ b/prompts/REPO_POLICIES.md @@ -1,6 +1,6 @@ --- title: Repository Policies -last_modified: 2026-02-22 +last_modified: 2026-03-09 --- This document covers repository structure, tooling, and workflow standards. Code @@ -98,6 +98,13 @@ style conventions are in separate documents: `https://git.eeqj.de/sneak/prompts/raw/branch/main/.gitignore` when setting up a new repo. +- **No build artifacts in version control.** Code-derived data (compiled + bundles, minified output, generated assets) must never be committed to the + repository if it can be avoided. 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. + - Never use `git add -A` or `git add .`. Always stage files explicitly by name. - Never force-push to `main`. -- 2.49.1