Skip to content

ci(triage): use pull_request_target so labeler can write on fork PRs #2850

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
setchy merged 2 commits into from
May 8, 2026
+11 −2
Merged

ci(triage): use pull_request_target so labeler can write on fork PRs #2850

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1a2ad13
ci(triage): use pull_request_target so labeler can write on fork PRs
afonsojramos May 7, 2026
3f55607
ci(triage): document pull_request_target rationale and silence zizmor
afonsojramos May 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions .github/workflows/triage.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,16 @@
name: Triage PR

on:
pull_request:
# `pull_request_target` is required so the labeler/title-validator can
# write labels and statuses on PRs from forks (under `pull_request`,
# GitHub forces GITHUB_TOKEN to read-only for fork PRs). Safe here
# because this workflow:
# - never checks out PR code (no actions/checkout),
# - has no `run:` steps that interpolate PR fields,
# - only invokes SHA-pinned actions that read PR metadata via the API,
# - is locked behind required code-owner review (see .github/CODEOWNERS)
# so future edits cannot quietly add privileged execution surface.
pull_request_target: # zizmor: ignore[dangerous-triggers]
branches:
- main
types:
Expand Down Expand Up @@ -29,7 +38,7 @@ jobs:
runs-on: ubuntu-latest
permissions:
contents: read # the config file
pull-requests: write # for labeling pull requests (on: pull_request_target or on: pull_request)
pull-requests: write # for labeling pull requests
statuses: write # to generate status
checks: write # to generate status
steps:
Expand Down
Loading