Repository navigation
Conversation
Adding `use project ci` by hand left the pull request mergeable on its fork result until the next monitor run, and did not start project CI. The pull_request_target revoke that closed the gap was dropped because that trigger is being disabled, so the maintainer's own command now withholds the result before adding the label, then restarts the pull request. Generated-by: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01NyQq9U7i5HhjDgrQ9qd3gq
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
November 15, 2026 19:33
This branch has not been deployed
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.
Adding
use project ciby hand has two gaps:CI passedsuccess posted before the label still lets the pull request merge until then, auto-merge included. Move XCom filter param models into execution API datamodels #76536 merged this way.#76672 first closed the window with a
pull_request_targetworkflow. That was dropped because the trigger is being disabled for the repository, and the window became a documented limitation.This adds two maintainer commands, run with the maintainer's own
ghcredentials.breeze ci use-project-ci <PR>does, in this order:CI passedis a fork CI success, sets it topending("Waiting for project CI (use project ci)"). This is the same status, link and description the monitor writes when it releases the pull request, so its next run changes nothing. A success that project CI earned is kept.use project ci, and removesuse fork ciif present.--no-restartleaves that to the author's next push.Because the success is withheld before the label is added, there is no moment at which the pull request carries the label and can still merge on the fork result.
breeze ci use-fork-ci <PR>removesuse project ciand addsuse fork ci. The monitor gates the pull request on its next run, and aCI passedthat project CI earned stays.Both commands:
--github-repositoryand--dry-run;GitHubClientgets areopenmethod. The commands are documented indev/breeze/doc/08_ci_tasks.rst, with regenerated command images. The triage guide and the design doc's note on this window are rewritten in #77133. Once both are merged, I'll update them to point touse-project-ci.Tested:
dev/breeze/tests/test_fork_ci_pr_move.py(new) covers the order of the writes, the statuses that must not be withheld, label changes, a closed pull request, and the commands' arguments and errors. Thereopentest is intest_fork_ci_github.py.Not yet run against a real pull request.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 5) following the guidelines
🤖 Generated with Claude Code
https://claude.ai/code/session_01NyQq9U7i5HhjDgrQ9qd3gq