ge-aerospace/shopdb-flask
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Dev setup: note GitHub has no CI yet, so local checks are the gate there
Some checks failed
CI / backend (push) Successful in 1m46s
Details
CI / naming (push) Successful in 1s
Details
CI / frontend (push) Successful in 8s
Details
CI / migrations-mysql (push) Failing after 8s
Details

Browse Source
This commit is contained in:
cproudlock
2026-07-17 15:09:16 -04:00
parent 9a60100cb2
commit 0e194c3237
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/DEVELOPMENT-SETUP.md
View File

@@ -182,10 +182,12 @@ tasks call `venv/` and `frontend/node_modules`).
bash scripts/check-naming-and-style.sh # naming - runs via Git Bash 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 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 VS Code task). On the internal server, CI runs all three on every push
if a name is wrong, so nothing bad reaches `main`; running them locally and fails the build on a bad name. GitHub Actions is not set up on the
just saves the round trip. The naming check is a shell script, so that public mirror yet, so if you develop against GitHub these local checks
one line needs Git Bash (installed with Git for Windows). (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: Want it automatic? The repo ships a hook; enable it once per clone:
```powershell ```powershell