From 2989e8e23e5b08d09e3a5daa5bfeda94976c9bad Mon Sep 17 00:00:00 2001 From: Jessey van Offeren Date: Fri, 22 May 2026 14:42:41 +0200 Subject: [PATCH] ci: run tests.yml on pull_request only (no push) to avoid double runs A branch with an open PR triggered both the push and pull_request events, running every job twice. Trigger on pull_request only; pushes to main are already tested by release.yml's `test` job. No version bump (CI config only). Co-Authored-By: Claude Opus 4.7 (1M context) --- .gitea/workflows/tests.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.gitea/workflows/tests.yml b/.gitea/workflows/tests.yml index 0960d07..bc8301b 100644 --- a/.gitea/workflows/tests.yml +++ b/.gitea/workflows/tests.yml @@ -1,14 +1,15 @@ name: tests run-name: Run test suite -# Runs the unittest suite on every push and pull request. Two jobs: +# Runs the unittest suite on pull requests (once per PR). Pushes to main are covered by the +# `test` job in release.yml, so we don't trigger on push here — that would double every run. +# Two jobs: # core — stdlib-only install; the GUI tests skip (@skipUnless HAVE_QT). Bulletproof. # gui-smoke — installs the GUI extra + offscreen Qt libs and runs the same suite headless, # exercising the MainWindow/SetupWizard/DiagnosticDialog construction tests. -# Make `core` a required status check on `main` so a PR can't merge with failing tests. +# Make `tests / core (pull_request)` a required status check on `main` so a PR can't merge red. on: - push: pull_request: jobs: