Repository navigation
ci(risk): Move the PR risk check to the classifiers action - #6677
Open
stephanie-anderson wants to merge 2 commits into
Open
stephanie-anderson wants to merge 2 commits into
stephanie-anderson wants to merge 2 commits into
Conversation
The risk classifier moved from getsentry/sdk-pr-risk-action to the internal getsentry/classifiers repository. A public repository cannot call an action in an internal one directly, so the workflow now gets a short-lived, read-only app token, checks the classifiers out at a pinned commit and runs the action from that checkout. Classification is unchanged. Two things are new: the action skips runs started by a title or description edit when the PR already has a risk label, and it keeps one summary comment on the PR with the label and its reasons. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
stephanie-anderson
requested review from
markushi and
runningcode
and removed request for
a team
November 19, 2026 08:13
📲 Install BuildsAndroid
|
The token action deprecates app-id in favour of client-id. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📜 Description
Replaces
.github/workflows/pr-risk-jev.ymlwith.github/workflows/pr-classifiers.yml.The risk classifier moved from
getsentry/sdk-pr-risk-actionto the internalgetsentry/classifiersrepository. A public repository cannot call an action in an internal one with a plainuses:line, so the workflow now:getsentry/classifiers,.classifiers,How a pull request is classified is unchanged: the same rubric, the same sentry-java fact sheet and the same rules as before. The request sent to the model was compared between the old and the new repository for 20 open pull requests, five of them from sentry-java, and is byte-identical.
What changes for this repo:
low, it lists the rules and the files that triggered them. When the model itself chose medium or high, it names the main concerns.pr-classifiers-<number>.💡 Motivation and Context
The classifier is being set up to hold more than the risk check and to serve more repositories, and it moved to its own repository for that.
getsentry/sdk-pr-risk-actionwill be archived once its callers have moved; this is the first one.💚 How did you test it?
The action has unit tests and runs in the classifiers repository's own CI. Not yet run anywhere: this caller shape (app token, checkout, action run from the checkout), the summary comment against the live API, and the skip for title edits. This repository is the first to use them.
Because the workflow uses
pull_request_target, it does not run on this pull request. It takes effect after merge. After merging I will check on a test pull request that:edit_ignoredand leaves the label,If the first run fails in the token or checkout step, every pull request shows a red "PR classifiers" check until it is fixed. It is not a required check, and reverting this pull request restores the previous workflow.
📝 Checklist
sendDefaultPIIis enabled.#skip-changelog
🤖 Generated with Claude Code