Skip to content

release: v4.30.3 - stop the skipped PR-run mirror from satisfying… - #347

Merged
Shinrai merged 4 commits into
masterfrom
next
Oct 2, 2026
Merged

Shinrai merged 4 commits into
masterfrom
next

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

No new features

🐛 Bug Fixes

📦 Dependencies

No dependency updates

🔧 Other Changes

👥 Contributors

Co-authored-by: Shinrai Shinrai@users.noreply.github.com

Shinrai and others added 4 commits October 2, 2026 13:31
…heck

On an in-repo feature PR, the `pull_request` run of ci.yml skips the
`required-check` job because the push run owns the status. A skipped job
still posts a check run under its name, and GitHub treats a skipped
required check as satisfied. The push run's real mirror is only created
once `ci` finishes, so for the whole test window the only check named
`✅ Required PR Check` on the head SHA was the skipped one — the ruleset
(and auto-merge) let the PR merge while tests were still running, gated
only by CodeQL. Seen on CLDMV/slothlet#553.

Give the job a conditional name: the real name on the paths that run,
`⏭️ Required PR Check (reported by the push run)` on the skipped path, so
the required check stays pending until the push run reports. Applied to
the consumer template and to this repo's local-ci.yml.
…heck (#346)

## 🚀 What's Changed

### 💥 Breaking Changes
_No breaking changes_

### ✨ Features
_No new features_

### 🐛 Bug Fixes
- fix(ci): stop the skipped PR-run mirror from satisfying Required PR
Check (#346) (6bcf11d)

### 📦 Dependencies
_No dependency updates_

### 🔧 Other Changes
- docs(ci): note that a skipped job's expression name is shown
unevaluated (#346) (f8dcf5a)



<details>
<summary>👥 Contributors</summary>

- @Shinrai

</details>
@cldmv-bot cldmv-bot Bot added ! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes type: bug Something is broken or not behaving as expected type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files labels Oct 2, 2026
@Shinrai
Shinrai enabled auto-merge (squash) October 2, 2026 20:47
@Shinrai
Shinrai merged commit 722b429 into master Oct 2, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes type: bug Something is broken or not behaving as expected type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant