krz/hutch

an ios client for sourcehut

clone: git clone https://gitbay.org/krz/hutch.git

db8539798766a6d238e7c134458f692c394e1668

verified · cmc

author: Christian Cleberg <hello@cleberg.net> · 2026-07-16T16:39:43Z

ci: drop the redundant post-merge test run

The suite ran on push to main and on pull_request. Since merges here are
merge commits (not squash) and pull_request tests the merge result, a
green PR already validates the exact tree that lands on main — the push
run just re-confirmed it on a macOS runner. Trigger on pull_request (and
workflow_dispatch) only.

 .github/workflows/test.yml | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index 9b03336..c002514 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -8,13 +8,20 @@ name: Tests
 # source directory still runs the suite. A skip rule that is too broad is how a
 # real change slips through ungated.
 #
-# Safe on pull_request only because main has no required status checks: a run
+# pull_request only, by design. GitHub runs the suite against the merge result
+# (PR merged into main), so a green PR already validates exactly what lands on
+# main. Merges here are merge commits, not squash, so the merged main is the same
+# tree that was tested — re-running on push to main would only burn a macOS runner
+# to re-confirm a result we already have.
+#
+# The tradeoff: a non-docs change pushed straight to main (bypassing a PR) is not
+# tested. That is not how this repo works — only docs go direct to main, and those
+# are path-skipped anyway.
+#
+# Safe as pull_request-only because main has no required status checks: a run
 # skipped by a path filter never reports, so a required check would leave a
 # docs-only PR waiting forever.
 on:
-  push:
-    branches: [main]
-    paths-ignore: ['*.md', 'Docs/*.md']
   pull_request:
     paths-ignore: ['*.md', 'Docs/*.md']
   workflow_dispatch: