You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The workflow template suggested when installing actions/labeler from a project's "New workflow" button results in a workflow using the pull_request event (instead of pull_request_target) that causes issues such as #446, #399, #136 and others.
To reproduce, go to a project and choose the Actions tab. Click the New workflow button, enter labeler into the Search workflows box and click Configure in the Label entry. This is the template that's given to submit:
# This workflow will triage pull requests and apply a label based on the# paths that are modified in the pull request.## To use this workflow, you will need to set up a .github/labeler.yml# file with configuration. For more information, see:# https://github.com/actions/labelername: Labeleron: [pull_request]jobs:
label:
runs-on: ubuntu-latestpermissions:
contents: readpull-requests: writesteps:
- uses: actions/labeler@v4with:
repo-token: "${{ secrets.GITHUB_TOKEN }}"
Note the use of pull_request instead of pull_request_target.
The text was updated successfully, but these errors were encountered:
The workflow template suggested when installing actions/labeler from a project's "New workflow" button results in a workflow using the
pull_request
event (instead ofpull_request_target
) that causes issues such as #446, #399, #136 and others.To reproduce, go to a project and choose the Actions tab. Click the New workflow button, enter
labeler
into the Search workflows box and click Configure in the Label entry. This is the template that's given to submit:Note the use of
pull_request
instead ofpull_request_target
.The text was updated successfully, but these errors were encountered: