Commit 7460722
authored
build: stop running PR title check on synchronize (#203)
## Problem
The PR Title Check registers as failing on some PRs even though the
title conforms — see #198. The check ends up with **two check-runs of
the same name on the head commit**, one `SUCCESS` and one `CANCELLED`,
and GitHub's status rollup treats the cancelled one as not-passing.
## Root cause
When Dependabot rebases a PR it force-pushes a new commit **and**
updates the PR body in the same instant. That fires two
`pull_request_target` events nearly simultaneously:
- `synchronize` — from the force-push
- `edited` — from the body update
Both resolve to the same concurrency group (`PR Title Check-<pr
number>`), so `cancel-in-progress: true` cancels the first run when the
second starts. Both runs had already created check-runs with identical
names, leaving a dangling `CANCELLED` check-run alongside the successful
one on the head commit.
The concurrency config works as intended for superseding *older
commits*; it only backfires when two events land on the *same* commit.
## Fix
The check only validates the PR title and description, and neither
changes on a push. So `synchronize` is both semantically unnecessary and
the specific trigger racing against `edited`. Trigger only on `opened`,
`edited`, and `reopened` — the events that actually change what's being
validated.
🤖 Generated with AI1 parent 702e045 commit 7460722
1 file changed
Lines changed: 7 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
4 | 10 | | |
5 | | - | |
| 11 | + | |
6 | 12 | | |
7 | 13 | | |
8 | 14 | | |
| |||
0 commit comments