Skip to content

Use draft release PRs to trigger CI via ready_for_review#6

Merged
eshork merged 1 commit intomainfrom
fix/draft-release-prs
Apr 26, 2026
Merged

Use draft release PRs to trigger CI via ready_for_review#6
eshork merged 1 commit intomainfrom
fix/draft-release-prs

Conversation

@eshork
Copy link
Copy Markdown
Collaborator

@eshork eshork commented Apr 26, 2026

Summary

  • Configure release-plz to create draft PRs (pr_draft = true)
  • Add ready_for_review event type to CI workflow trigger

Why

Release PRs created by GITHUB_TOKEN don't trigger other workflows (GitHub's anti-recursion rule). Instead of manual commit-status plumbing or extra credentials, we use draft PRs: the human "Ready for review" action is attributed to the user, which triggers CI normally.

Changes

File Change
release-plz.toml Add pr_draft = true
.github/workflows/ci.yml Add ready_for_review to pull_request event types

Flow

  1. Push to main → release-plz creates a draft release PR
  2. Maintainer reviews version bumps and changelog
  3. Maintainer marks PR "Ready for review" → CI fires (Test workspace, Clippy, docs, MSRV)
  4. Checks pass → PR is mergeable
  5. Merge → release-plz publishes to crates.io via OIDC

Fixes the "Test workspace" check gate issue on release PR #4.

release-plz now creates draft PRs (pr_draft = true). When a user
marks the PR ready for review, that user action triggers the normal
CI workflow—no manual commit-status plumbing or PAT needed.

ci.yml gains the ready_for_review event type so the Test workspace
check fires on the transition from draft to ready.
@eshork eshork merged commit 00d8efd into main Apr 26, 2026
4 checks passed
@eshork eshork deleted the fix/draft-release-prs branch April 26, 2026 03:15
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