Repository navigation
ci(risk): Never label PRs touching high-risk files as low risk - #6643
Merged
Merged
Conversation
Co-Authored-By: Nelson Osacky <nelson.osacky@sentry.io>
📲 Install BuildsAndroid
|
runningcode
approved these changes
Nov 17, 2026
runningcode
marked this pull request as ready for review
November 17, 2026 15:20
runningcode
requested review from
markushi and
romtsn
and removed request for
a team
November 17, 2026 15:20
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.
.github/file-filters.ymlalready lists the files we treat as high risk: the transport classes,RateLimiter, andInternalSentrySdk, which hybrid SDKs use. "Changes In High Risk Code" comments on PRs that touch them, but the PR Risk (Jev) workflow never looks at that list. A PR that changesRateLimitercould still getrisk: low.Now the publish step raises a Jev
lowtorisk: mediumwhen the PR touches one of those files, and logs a notice naming them. Medium and high verdicts are left alone. Jev's own rubric says sensitive paths shouldn't decide the label on their own, so this applies the repo's policy after classification instead of changing the model input.The filter is read from the PR's base revision, so a PR can't remove its own files from the list. The parser accepts exact paths only. If someone adds a glob, the job fails instead of silently missing it.
file-filters.ymlnow has a comment saying so.Open decision: medium vs. high as the minimum. I went with medium, since these files are only one signal. Changing it is a one-word edit.
Like any
pull_request_targetworkflow, this runs frommain, so it takes effect only after merge.#skip-changelog
via no.
--
View Session [Sentry]