fix: auto-trigger CI checks on release-please PR updates#24
Merged
GraysonCAdams merged 1 commit intomainfrom Mar 1, 2026
Merged
fix: auto-trigger CI checks on release-please PR updates#24GraysonCAdams merged 1 commit intomainfrom
GraysonCAdams merged 1 commit intomainfrom
Conversation
When release-please updates its PR via GITHUB_TOKEN, the pull_request_target synchronize event doesn't always fire. Add a close/reopen step to the release workflow that ensures the reopened event triggers CI checks reliably.
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
trigger-pr-checksjob to the release workflow that closes and reopens the release-please PR after it's created/updatedpull_request_targetreopenedevent fires reliably, triggering CI and CodeQL checkssynchronizeevents from GITHUB_TOKEN don't consistently triggerpull_request_target, leaving release PRs with no status checks and unable to mergeThe ideal long-term fix is using a fine-grained PAT for release-please (noted in a comment), but this close/reopen approach works immediately without any external credential setup.
Test plan