fix: rerun checks for refreshed release PRs#30
Merged
Conversation
Change-Id: Ib3e39f70817a1cb90fe446fc32b40907ab58faa2 Signed-off-by: Thomas Kosiewski <tk@coder.com>
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
action_requiredruns created whenGITHUB_TOKENrefreshes release PR branchesWhy
PR #29 fixed the merge conflict by rebuilding sibling release PRs on the latest
main. GitHub intentionally marks workflows triggered by a bot-authoredGITHUB_TOKENbranch update asaction_required; without a rerun, those refreshed PRs would still need a manual click. This finishes the no-intervention flow.Validation
pnpm --filter @coder/release-please-ai test:unit(10 tests)pnpm --filter @coder/release-please-ai typecheckpnpm checkGenerated with
mux• Model:openai:gpt-5.6-sol• Thinking:max