ci: use pull_request_target for PR triage workflow - #2237
Conversation
Fork PRs get a read-only GITHUB_TOKEN under pull_request, which breaks requestReviewers (needs pull-requests: write). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Benchmark reportthis PR + run time: 1 faster
compile time: unchanged across 32 benchmarksSignificant changes (1) ──────── run time ─────── ───── compile time ─────
benchmark baseline this PR Δ baseline this PR Δ
───────────────────────────────────────────────────────────────────────────────
+ categorical_log_prob 2.5 ms 2.2 ms -10.7% 75.2 ms 74.2 ms -1.3%Red is slower, green is faster; a row is coloured by the worse of its two columns. A delta in parentheses cleared the threshold on a measurement below the resolution floor, so it is shown without being called a change. † marks a benchmark that could not be compared — see below. Full results
|
| baseline | this PR | |
|---|---|---|
| ref | master |
fix-pr-triage |
| commit | a47333ee |
744fbcde |
| numpyro | 0.21.0 | 0.21.0 |
| jax | 0.11.0 | 0.11.0 |
| backend | cpu | cpu |
| python | 3.14.6 | 3.14.6 |
Runner: Linux-6.17.0-1020-azure-x86_64-with-glibc2.39, 4 CPUs.
Produced by this benchmark run.
Fork PRs get a read-only GITHUB_TOKEN under pull_request, which breaks requestReviewers (needs pull-requests: write).