From acd568f5d33c9fe70380dcb56dc0e79cf564fefa Mon Sep 17 00:00:00 2001
From: feder-cr <85809106+feder-cr@users.noreply.github.com>
Date: Wed, 20 May 2026 13:25:08 -0700
Subject: [PATCH] ci: add pre-push hook to block red pushes

git config core.hooksPath .githooks (one-time per clone).
Runs pytest with the default markers (unit + integration) and refuses
to push if anything fails. ~2s overhead per push.

Bypass for emergency WIP with --no-verify; never on release branches.
---
 .githooks/pre-push | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 .githooks/pre-push

diff --git a/.githooks/pre-push b/.githooks/pre-push
new file mode 100644
index 0000000..e21b917
--- /dev/null
+++ b/.githooks/pre-push
@@ -0,0 +1,31 @@
+#!/bin/sh
+# Pre-push hook: blocks push if the test suite isn't fully green.
+#
+# Enable once with:
+#   git config core.hooksPath .githooks
+#
+# Bypass for a known-broken WIP push (NOT for releases):
+#   git push --no-verify
+# The --no-verify flag is the only escape hatch. Use it sparingly and never
+# for branches that feed into a release.
+
+set -e
+
+echo "[pre-push] running unit + integration tests before push..."
+
+# Run from this script's directory so it works regardless of where the user
+# invoked git push from.
+cd "$(dirname "$0")/.."
+
+# Default pyproject addopts skip slow/e2e. That's the gate we want for every
+# push — fast feedback. e2e is reserved for explicit release runs.
+if ! python -m pytest -q --tb=short; then
+    echo ""
+    echo "[pre-push] TESTS FAILED — push aborted."
+    echo "[pre-push] Either fix the failure or use 'git push --no-verify' if"
+    echo "[pre-push] you really know what you're doing (NOT for release branches)."
+    exit 1
+fi
+
+echo "[pre-push] all tests green — push proceeding."
+exit 0