Open
Conversation
Only post a severity classification comment when the bot hasn't commented before or when the severity actually changed. Previously every push (synchronize event) would post a new comment even if the classification was identical. The prompt now instructs the classifier to: - Check for existing bot comments via the pr-severity-bot marker - Compare the new severity against the existing severity label - Skip commenting if both match, while still ensuring labels are correct - Include a severity changed banner when re-commenting due to a change
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
Collaborator
🟢 PR Severity: LOW
🟢 Low (1 file)
AnalysisThis PR modifies only the GitHub Actions workflow configuration for the PR severity bot itself. Changes to CI/CD configuration files in
The change appears to reduce comment spam from the severity bot, which is a pure quality-of-life improvement for the development workflow. No severity bumps applied: Single file change with <500 lines. To override, add a |
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
2 participants
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.
The PR severity classifier currently posts a new comment on every
push to a PR, even when the classification hasn't changed. On active
PRs with many pushes this creates a wall of identical bot comments.
This change updates the classifier prompt to check for existing bot
comments (via the pr-severity-bot HTML marker) and compare the newly
determined severity against the PR's current severity label before
deciding whether to comment.
A comment is now only posted when the bot hasn't commented before or
when the severity actually changed. Labels are still always kept in
sync regardless of whether a comment is posted.
When severity does change between classifications, the new comment
includes a banner showing the old and new severity levels so
reviewers can see what shifted and why.