Repository navigation
Conversation
Copilot
AI
changed the title
[WIP] Fix explicit target consumption in push_to_pull_request_branch
Clarify explicit PR targets rejected by triggering-only push configuration
Oct 2, 2026
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.
On scheduled runs,
push_to_pull_request_branchcould report that target"triggering"lacked PR context even when the caller supplied a PR number. The error did not explain why that number was ignored.pull_request_numberand explain that per-call PR targeting requirestarget: "*".target: "triggering"context-bound; a per-call number does not override the workflow configuration.