ai_qc/backend/scripts
nickviljoen a3b3f45f01 fix(deploy): use git's own -n limit instead of | head -20
When the deploy batch has more than 20 commits, the `git log ... | head -20`
pipeline closes the pipe after 20 lines. git log gets SIGPIPE (exit 141),
which `set -o pipefail` propagates, and `set -e` then exits the script
silently — no prompt shown, no error message.

Only bites for release-sized batches (>20 commits). First seen on the
v1.3.0 prod deploy: 20 commits displayed, then the script returned to
the shell without prompting. dev deploys never hit this because they
typically only have 1-3 commits ahead.

Fix: tell git to limit its own output via `-n 20`. Same display, no
broken pipe. Also swap the count-by-wc-l for `git rev-list --count`
which is more idiomatic and avoids any further pipe shenanigans.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-17 15:25:38 +02:00
..
box_setup.py feat(box-jwt): add box_setup.py bootstrap CLI for webhook management 2026-05-14 22:53:03 +02:00
deploy.sh fix(deploy): use git's own -n limit instead of | head -20 2026-05-17 15:25:38 +02:00
health-check.sh Add manual deploy/rollback/health scripts; remove stale rsync deploy 2026-04-22 18:34:26 +02:00
rollback.sh Add manual deploy/rollback/health scripts; remove stale rsync deploy 2026-04-22 18:34:26 +02:00
run-local.sh Create frontend and backend folder structure for deployment 2025-11-06 11:55:53 +02:00
test-system.sh Create frontend and backend folder structure for deployment 2025-11-06 11:55:53 +02:00