Skip to content

chore(deps): bump the npm_and_yarn group across 1 directory with 3 updates #7059

chore(deps): bump the npm_and_yarn group across 1 directory with 3 updates

chore(deps): bump the npm_and_yarn group across 1 directory with 3 updates #7059

name: Assign requested reviewers

Check warning on line 1 in .github/workflows/assign_reviewers.yml

View workflow run for this annotation

GitHub Actions / Assign requested reviewers

Workflow execution policy warning (evaluate mode)

On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target
# This workflow adds requested reviewers as assignees. If you remove a
# requested reviewer, it will not remove them as an assignee.
#
# See https://github.com/google/blockly/issues/5643 for more
# information on why this was added.
#
# N.B.: Runs with a read-write repo token. Do not check out the
# submitted branch!
on:
pull_request_target:
types: [review_requested]
jobs:
requested-reviewer:
runs-on: ubuntu-latest
if: ${{ github.event.requested_reviewer != null }}
permissions:
pull-requests: write
steps:
- name: Assign requested reviewer
uses: actions/github-script@v9
with:
script: |
try {
if (context.payload.pull_request === undefined) {
throw new Error("Can't get pull_request payload. Check that " +
"a request reviewer event was triggered.");
}
const {number: issue_number} = context.payload.pull_request;
await github.rest.issues.addAssignees({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: issue_number,
assignees: [context.payload.requested_reviewer.login]
});
} catch (error) {
core.setFailed(error.message);
}