From 0e194c3237cd04891e5c500fed1f9d66a310b657 Mon Sep 17 00:00:00 2001 From: cproudlock Date: Fri, 17 Jul 2026 15:09:16 -0400 Subject: [PATCH] Dev setup: note GitHub has no CI yet, so local checks are the gate there --- docs/DEVELOPMENT-SETUP.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/DEVELOPMENT-SETUP.md b/docs/DEVELOPMENT-SETUP.md index fad2650..753a440 100644 --- a/docs/DEVELOPMENT-SETUP.md +++ b/docs/DEVELOPMENT-SETUP.md @@ -182,10 +182,12 @@ tasks call `venv/` and `frontend/node_modules`). bash scripts/check-naming-and-style.sh # naming - runs via Git Bash ``` There is NO auto-installed git hook - you run these yourself (or the - VS Code task). CI runs all three on every push and will fail the build - if a name is wrong, so nothing bad reaches `main`; running them locally - just saves the round trip. The naming check is a shell script, so that - one line needs Git Bash (installed with Git for Windows). + VS Code task). On the internal server, CI runs all three on every push + and fails the build on a bad name. GitHub Actions is not set up on the + public mirror yet, so if you develop against GitHub these local checks + (or the opt-in hook below) are your only gate - run them. The naming + check is a shell script, so that one line needs Git Bash (installed with + Git for Windows). Want it automatic? The repo ships a hook; enable it once per clone: ```powershell