Repository navigation
release.ps1: wait for the PR's own CI run - #108
Merged
Merged
Conversation
A release PR's pull_request run is registered seconds after the PR opens. Until then GitHub calls the PR clean on the push run of the same commit, and the merge then meets the new run: Release 1.3.0 was refused 'the base branch policy prohibits the merge' on 2026-10-28. Wait-PrCheck now waits for that run to exist and pass before checking mergeStateStatus.
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.
Promoting v1.3.0-beta.5 stopped at the merge of the release PR: the PR's own
pull_requestrun had just been registered, after GitHub had already called the PR clean on the push run of the same commit (same check names), and GitHub refused the merge ("the base branch policy prohibits the merge").Wait-PrChecknow waits for the PR's own run of build.yml to exist and pass before it checksmergeStateStatus.-SelfTestpasses (57 cases); the network part is exercised by the next promotion.