Repository navigation
chore: start the review bot on pull_request_target again - #547
Merged
Pavel Feldman (pavelfeldman) merged 1 commit intoNov 18, 2026
Merged
Conversation
Pavel Feldman (pavelfeldman)
deleted the
agent-review-pull-request-target
branch
November 18, 2026 18:39
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.
This puts
agent-review.ymlback onpull_request_target. It undoes the move topull_request.pull_requestdoes not start a run when the PR has a merge conflict, so theagent-reviewlabel did nothing on such a PR.pull_request_targetruns from the default branch and has no such limit. The workflow never checks out the PR.GitHub blocks
pull_request_targetin public repositories from December 2, 2026, unless an Actions policy of the repo allows it. The repo needs a policy that allows the event for this workflow. See Securely using pull_request_target.