Repository navigation
devops(bots): let a publish-calls pull request go to a branch - #43892
Merged
Pavel Feldman (pavelfeldman) merged 1 commit intoNov 4, 2026
Merged
Conversation
Yury Semikhatsky (yury-s)
approved these changes
Nov 3, 2026
Contributor
Test results for "tests 1"1 flaky23585 passed, 704 skipped Merge workflow run. |
Contributor
Test results for "MCP"5194 passed, 616 skipped Merge workflow run. |
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
pull-requestcall ofpublish-callstakes an optionalbase: the branch that the PR goes to. Without it, the PR goes to the default branch, as before, so the other bot repos need no change.publish-patchhad this as an input. playwright-python needs it to roll from a release branch:roll.ymlin devops(roll): open the pull request with publish-calls playwright-python#3317 can setbaseafter this lands.