From c4ef989e1a0d764aa4b35a74c2ede842f6c6a7b0 Mon Sep 17 00:00:00 2001 From: Nicolas Date: Mon, 17 Aug 2026 23:14:46 +0200 Subject: [PATCH] ci: drop pull_request trigger, push alone covers same-repo PRs push (all branches) already fires for a PR branch on this repo; keeping pull_request too just ran every job twice on the same commit. GitHub still attaches the push-triggered run to the PR by SHA regardless of which event fired it. Co-Authored-By: Claude Sonnet 5 --- .github/workflows/ci.yml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 8158311..f6faf44 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -1,13 +1,15 @@ name: CI # Every push, on every branch — not just main — so build breakage shows up -# on the first commit of a branch, not only once a PR targets main. -# pull_request is kept alongside push for fork PRs, where push events never -# reach this repo. +# on the first commit of a branch, not only once a PR targets main. No +# separate pull_request trigger: for a PR from a branch on this same repo, +# push already fires on that branch, and GitHub attaches the run to the PR +# by commit SHA regardless of which event triggered it — adding +# pull_request too would just run every job twice per push. (Re-add it, +# scoped to forks, only if this repo starts accepting fork PRs — push +# events from a fork never reach here.) on: push: - pull_request: - branches: [main] env: DATABASE_URL: "postgresql://ci:ci@localhost:5432/batchcooking_ci?schema=public"