Skip to content

chore: start the review bot on pull_request_target again - #3354

Merged
Pavel Feldman (pavelfeldman) merged 1 commit into
mainfrom
agent-review-pull-request-target
Nov 18, 2026
Merged

Pavel Feldman (pavelfeldman) merged 1 commit into
mainfrom
agent-review-pull-request-target

Conversation

@pavelfeldman

@pavelfeldman Pavel Feldman (pavelfeldman) commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

This puts agent-review.yml back on pull_request_target. It undoes the move to pull_request.

pull_request does not start a run when the PR has a merge conflict, so the agent-review label did nothing on such a PR. pull_request_target runs from the default branch and has no such limit. The workflow never checks out the PR.

The job still skips a PR from a fork. The bot cannot push to a fork, so no token is made and no run starts for it.

GitHub blocks pull_request_target in 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.

@pavelfeldman
Pavel Feldman (pavelfeldman) merged commit 6137272 into main Nov 18, 2026
34 checks passed
@pavelfeldman
Pavel Feldman (pavelfeldman) deleted the agent-review-pull-request-target branch November 18, 2026 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants