[no-ci] Clarify policy for explicitly requested upstream pushes - #2645
Open
rwgk wants to merge 1 commit into
Open
[no-ci] Clarify policy for explicitly requested upstream pushes#2645rwgk wants to merge 1 commit into
rwgk wants to merge 1 commit into
Conversation
rwgk
added
documentation
Contributor
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
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.
Description
Follow-up to #2378.
The current policy makes the canonical upstream repository unconditionally read-only. That remains the right default for normal pull-request work, but the absolute wording creates significant friction for a small set of valid, user-directed workflows. In practice, agents have repeatedly asked me to perform a push manually even when I explicitly requested it and upstream was needed to test
.github/workflows, trigger CI from a designated ref, or support similar infrastructure work.This change keeps approved forks as the normal destination and permits an upstream push only when the user explicitly requests it and provides a rationale. It also requires verification of the complete repository and exact refspec, limits authorization to the requested ref update, and requires separate explicit authorization for higher-risk operations.
This is not intended to give agents more autonomy. The agent does not infer when an upstream push is appropriate: the user supplies the request and rationale. The instructions only allow the agent to execute that narrowly scoped request instead of requiring a manual handoff.