Skip to content

chore: lock file maintenance and fix new ty errors #97

chore: lock file maintenance and fix new ty errors

chore: lock file maintenance and fix new ty errors #97

name: Apify Pull Request Toolkit

Check warning on line 1 in apify/pull-request-toolkit-action/.github/workflows/run_action.yaml

View workflow run for this annotation

GitHub Actions / Apify Pull Request Toolkit

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
on:
# Gives fork runs the secrets to close their issues on merge; safe since no pull request code is checked out.
pull_request_target:
types: ['opened', 'reopened', 'synchronize', 'labeled', 'unlabeled', 'edited', 'ready_for_review', 'closed']
# The action uses only the org token, so `GITHUB_TOKEN` (writable under `pull_request_target`) gets no permissions.
permissions: {}
concurrency: # This is to make sure that it's executed only for the most recent changes of the pull request.
# Keyed by pull request, since `github.ref` is the base branch under `pull_request_target`.
group: pull-request-toolkit-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
apify-pull-request-toolkit:
# This is to make sure that this workflow is only run when the action is used from a different repository.
# The workflow that tests the action against itself is in test_action.yaml.
if: github.repository != 'apify/pull-request-toolkit-action'
runs-on: ubuntu-22.04-arm64
steps:
- name: Apify Pull Request Toolkit
uses: apify/pull-request-toolkit-action@main
with:
org-github-token: ${{ secrets.PULL_REQUEST_TOOLKIT_ACTION_GITHUB_TOKEN }}
apify-api-token: ${{ secrets.ACTOR_GITHUB_CONTROLLER_APIFY_API_TOKEN }}