Skip to content

Add label-triggered PerfStar evaluation workflow - #15009

Draft
baronfel wants to merge 1 commit into
mainfrom
baronfel-perfstar-label-trigger
Draft

baronfel wants to merge 1 commit into
mainfrom
baronfel-perfstar-label-trigger

Conversation

@baronfel

@baronfel baronfel commented Sep 11, 2026

Copy link
Copy Markdown
Member

Summary

  • trigger PerfStar evaluation when PerfStar: Evaluate is added to a pull request
  • refresh the short-lived perf/pr-<number> branch whenever a tracked pull request is updated
  • remove generated branches when tracking ends or the pull request closes
  • avoid checking out or executing pull request code while retaining fork pull request support

Security

The workflow uses pull_request_target only for base-repository API access. It does not check out or execute pull request code, pins actions/github-script by SHA, and grants contents: write only to the jobs that update refs.

Zizmor 1.25.2 reports no findings (one documented dangerous-triggers exception).

Since only repo maintainers, triagers, and admins can modify labels, this makes it an explicit decision to run perf analysis on explicitly trusted PRs.

Deployment note

The PerfStar: Evaluate repository label must exist before this workflow can be used.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 14ed033f-1e07-462f-8116-97fdbf25e8bf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant