Skip to content

ci: run on push to main (fix stale red badge) #140

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
renaudcepre merged 1 commit into from
Jun 25, 2026
Merged

ci: run on push to main (fix stale red badge) #140

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
name: CI

on:
push:
branches: [main]
pull_request:
types: [opened, synchronize]

Expand Down
9 changes: 9 additions & 0 deletions JOURNAL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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,
Expand Down
Loading