ci: run pytest on PRs, not just push-to-main #13

New issue

Closed

opened 2026-05-03 14:48:01 +00:00 by gravityfargo · 0 comments

gravityfargo commented

2026-05-03 14:48:01 +00:00

Owner

Context

`.forgejo/workflows/test.yml` is filtered to `on: push: branches: [main]` — PRs do not trigger CI. As a result, breakage is only detected post-merge (latest example: run #11 failed after the Python 3.14 bump merged).

Plan

Add `pull_request` trigger so PRs to main run pytest before merge
Optionally: also keep the push trigger for direct main pushes
Look into run #11 failure (Python 3.14 + setup-uv@v7 — possibly runner image lag or an env-mismatch we should track separately)

Acceptance criteria

PRs trigger CI
Main CI back to green (separate root-cause investigation may be needed)

## Context \`.forgejo/workflows/test.yml\` is filtered to \`on: push: branches: [main]\` — PRs do not trigger CI. As a result, breakage is only detected post-merge (latest example: run #11 failed after the Python 3.14 bump merged). ## Plan - Add \`pull_request\` trigger so PRs to main run pytest before merge - Optionally: also keep the push trigger for direct main pushes - Look into run #11 failure (Python 3.14 + setup-uv@v7 — possibly runner image lag or an env-mismatch we should track separately) ## Acceptance criteria - [ ] PRs trigger CI - [ ] Main CI back to green (separate root-cause investigation may be needed)

gravityfargo added the

bug

label

2026-05-03 14:48:17 +00:00

gravityfargo referenced this issue from a commit

2026-05-03 14:55:23 +00:00

ci: run pytest on PRs + add concurrency dedupe

gravityfargo referenced this issue from a pull request that will close it,

2026-05-03 14:55:36 +00:00

ci: run pytest on PRs + add concurrency dedupe #14

gravityfargo closed this issue

2026-05-03 14:56:33 +00:00