Skip to content

ci: run CI on release-please PRs - #53

Merged
ngngardner merged 3 commits into
mainfrom
ci-release-please-dispatch
Oct 23, 2026
Merged

ngngardner merged 3 commits into
mainfrom
ci-release-please-dispatch

Conversation

@ngngardner

Copy link
Copy Markdown
Contributor

Release-please opens and updates its release PR with GITHUB_TOKEN, which starts no workflow, so the release PR never got the required check / check and could not merge without a bypass.

  • ci.yml: accept workflow_dispatch.
  • release-please.yml: pin the shared workflow to Emerging-Patterns/actions@5b1f535 (actions#10), grant actions: write (workflow and job), and pass ci-workflow: ci.yml. After release-please runs, it dispatches ci.yml on each open release PR head that has no CI run yet. The dispatched run's check job calls nix-flake-check.yml (job check), so it reports as check / check on the release PR head, matching the ruleset.

🤖 Generated with Claude Code

ngngardner and others added 3 commits October 23, 2026 14:07
release-please pushes its release branch with GITHUB_TOKEN, which starts
no workflow, so the release PR never got the required check / check. Pin
the shared release-please workflow to 5b1f535, which dispatches ci.yml on
the release branch (ci-workflow: ci.yml), grant it actions: write, and
let ci.yml run on workflow_dispatch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
c1e67a6 (actions#11) dispatches CI over the action_required pull_request
run that a github.token push leaves on the release branch head; 5b1f535
counted that run and skipped the dispatch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dec791a (actions#12) warns instead of failing the release-please job when
GitHub refuses the CI dispatch, e.g. on a release branch cut before
ci.yml accepted workflow_dispatch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ngngardner
ngngardner merged commit 4c0f2d8 into main Oct 23, 2026
1 check passed
@ngngardner
ngngardner deleted the ci-release-please-dispatch branch October 23, 2026 18:31
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