Repository navigation
ci: Skip duplicate high-risk code PR comments - #6010
Merged
Merged
Conversation
buenaflor
marked this pull request as ready for review
August 26, 2026 15:39
buenaflor
requested review from
0xadam-brown,
adinauer,
markushi,
romtsn and
runningcode
as code owners
August 26, 2026 15:39
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8af0c7b. Configure here.
📲 Install BuildsAndroid
|
Only post the high-risk code warning once per PR, matching sentry-dart. Co-Authored-By: Gino Buenaflor <giancarlo.buenaflor@sentry.io> Co-Authored-By: Roman Zavarnitsyn <roman.zavarnitsyn@sentry.io>
Avoid missing an existing warning when a PR has more than 30 comments. Co-Authored-By: Roman Zavarnitsyn <roman.zavarnitsyn@sentry.io>
Avoid TypeError if a PR comment has a null body. Co-Authored-By: Roman Zavarnitsyn <roman.zavarnitsyn@sentry.io>
Keep a single warning comment and refresh its body so reviewers do not see a stale high-risk file list after later pushes. Co-Authored-By: Roman Zavarnitsyn <roman.zavarnitsyn@sentry.io>
Only rewrite the warning when the high-risk file set changes, and keep reviewer checkbox state for files that remain. Co-Authored-By: Roman Zavarnitsyn <roman.zavarnitsyn@sentry.io>
Drop the leading space before the file list and allow optional indent so the first checklist item is not skipped on parse. Co-Authored-By: Roman Zavarnitsyn <roman.zavarnitsyn@sentry.io>
sentry-junior
Bot
force-pushed
the
ci/skip-duplicate-high-risk-comments
branch
from
November 6, 2026 12:48
61ef7a0 to
3e15390
Compare
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
Update the high-risk code workflow so it lists existing PR comments and only posts the warning if one is not already present. Matches the behavior in sentry-dart.
💡 Motivation and Context
On every push to a PR that touches high-risk files, the workflow created another identical comment. That spam is noisy for reviewers. Skip when a comment with the high-risk marker already exists.
💚 How did you test it?
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
#skip-changelog
Requested by Gino Buenaflor.
--
View Junior Session [Sentry]