docs(agents): pre-authorize changesets release pull requests - #76
Merged
Merged
Conversation
Merging a release pull request needed an explicit instruction for that PR, so an agent that merged a feature had to stop and ask before merging the release the workflow opened for it. That branch never goes green: its CI run sits at `action_required` and the runs that do execute fail, which is why the previous release PR was merged with a red board. The rule now names the exception, so the release is not gated on an answer that only exists in one session.
|
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.
Recording a rule that only existed inside one session.
Merging a pull request needs an explicit instruction for that specific pull request, with no exception for the release pull request the workflow opens. So an agent that merged a feature had to stop and ask before merging its release, and the answer lived nowhere durable.
The release branch never goes green: its CI run sits at
action_required, and the runs that do execute fail. The previous release pull request was merged with a red board anyway. The rule now names the exception, so a release is not gated on an answer someone has to give again next session.Only the second bullet changed; the general gate on normal pull requests is untouched.