Use draft release PRs to trigger CI via ready_for_review#5
Closed
Use draft release PRs to trigger CI via ready_for_review#5
Conversation
Adds release-plz configuration and GitHub Actions workflow for automated crates.io publishing via trusted publishing (OIDC). On push to main, release-plz creates a release PR with version bumps and changelogs. When the release PR is merged, it publishes crates in dependency order (libudx -> peeroxide-dht -> peeroxide) and creates GitHub releases with tags.
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.
Collaborator
Author
|
Stale branch base — recreating from current main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pr_draft = true)ready_for_reviewevent type to CI workflow triggerWhy
Release PRs created by
GITHUB_TOKENdon't trigger other workflows (GitHub's anti-recursion rule). Instead of working around this with manual status APIs or extra credentials, we use draft PRs: the human "Ready for review" action is attributed to the user, which triggers CI normally.Changes
release-plz.tomlpr_draft = true.github/workflows/ci.ymlready_for_reviewtopull_requestevent typesCloses the "Test workspace" check gate issue on release PR #4.