fix(ci): auto-trigger CI on release-please PR branch#58
Merged
Conversation
GITHUB_TOKEN events don't trigger other workflows, so the CI workflow never ran on the release-please branch, leaving required status checks perpetually pending. Now the Release workflow itself runs tests on the release-please branch and reports status checks via the GitHub API.
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
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
GITHUB_TOKENevents don't trigger other workflows, so the CI workflow never runs on the release-please branchHow it works
release-pr-cijob runsrelease-please--branches--masterbranch existsmake check(same as CI workflow)test (3.12)andtest (3.13)status checks on the branch HEAD SHATest plan
${{ }}expressions use env vars to prevent injection (GitHub Actions security best practice)