Skip to content

ci: skip pull_request runs for release-please output-only PRs - #39

Merged
kunchenguid merged 1 commit into
mainfrom
fm/release-ci-simplewords-r3
Jul 31, 2026
Merged

kunchenguid merged 1 commit into
mainfrom
fm/release-ci-simplewords-r3

Conversation

@kunchenguid

Copy link
Copy Markdown
Owner

Summary

  • Add paths-ignore on ci.yml's pull_request trigger for the exact release-please output set: .release-please-manifest.json, CHANGELOG.md, package.json, extension/manifest.json.
  • Add scripts/check-release-ci-exclusions.sh (config-derived, dependency-free) and wire it as an early CI step so drift fails loudly if release-please starts writing a new path.
  • push on main and release-please.yml are unchanged, so post-merge release/tag/publish behavior is untouched.

Why

Since 2026-07-01, GITHUB_TOKEN-opened release-please PRs create pull_request workflow runs that sit in action_required forever. Path filtering is the only native way to create zero runs. simplewords has not cut a release since that change, so this is pre-emptive.

Validation

Notes for merge

Direct-PR delivery per captain override for the release-please CI fleet rollout. No required status checks exist on this repo.

Exclude the exact release-please output set from ci.yml's pull_request
trigger so release PRs create zero runs instead of action_required ones.
Add a config-derived drift check as an early CI step.
@kunchenguid
kunchenguid merged commit 063c3ee into main Jul 31, 2026
1 check passed
@kunchenguid
kunchenguid deleted the fm/release-ci-simplewords-r3 branch July 31, 2026 06:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant