From 34218898c642e56d6b58db4096da2a2c03e43f86 Mon Sep 17 00:00:00 2001
From: Renaud Cepre <32103211+renaudcepre@users.noreply.github.com>
Date: Thu, 25 Jun 2026 05:26:27 +0200
Subject: [PATCH] ci: run on push to main

ci.yml only triggered on pull_request, so the default-branch CI badge was frozen
on the last push run (a failure from March) and showed red on the PyPI page even
though every PR was green. Adding a push trigger on main refreshes the badge on
each merge.
---
 .github/workflows/ci.yml | 2 ++
 JOURNAL.md               | 9 +++++++++
 2 files changed, 11 insertions(+)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 4c900bd..449fb31 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -1,6 +1,8 @@
 name: CI
 
 on:
+  push:
+    branches: [main]
   pull_request:
     types: [opened, synchronize]
 
diff --git a/JOURNAL.md b/JOURNAL.md
index 123b915..769c1bc 100644
--- a/JOURNAL.md
+++ b/JOURNAL.md
@@ -1,5 +1,14 @@
 # JOURNAL
 
+## 2026-06-25 — ci: run on push to main (badge CI rouge)
+
+Badge CI rouge sur la page PyPI : pas une regression. `ci.yml` ne se declenchait
+que sur `pull_request`, jamais sur push main, donc le badge fossilisait le dernier
+run push (un echec de mars 2026). Ajout du trigger `push: branches: [main]` : chaque
+merge relance la CI sur main et rafraichit le badge. Le code etait vert sur toutes
+les PRs. (Lie : les PRs release-please n'ont aucun check car les PRs du bot
+github-actions ne declenchent pas les workflows.)
+
 ## 2026-06-25 — ci(publish): apte publie sur PyPI, trigger release cable
 
 Trusted Publisher PyPI configure (pending publisher : repo=renaudcepre/apte,