You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To minimize unnecessary email notifications sent to all subscribers of a Pull Request, it would be beneficial to introduce an optional parameter that can prevent the creation of the "Scan Summary & Details" comment when no violations are found.
Current Behavior:
Under the current implementation, an email is sent each time these comments are created by the Action, regardless of whether any action is required. This results in redundant notifications that clutter the inboxes of PR subscribers.
Proposed Solution:
Add an optional parameter, similar to --github.ScanSubmittedComment=false, to control the generation of the "Scan Summary & Details" comment in case there are "No policy violation found" and "No package violation found", thereby reducing unnecessary email notifications and improving the user experience.
Thank you for considering this enhancement.
The text was updated successfully, but these errors were encountered:
Description
To minimize unnecessary email notifications sent to all subscribers of a Pull Request, it would be beneficial to introduce an optional parameter that can prevent the creation of the "Scan Summary & Details" comment when no violations are found.
Current Behavior:
Under the current implementation, an email is sent each time these comments are created by the Action, regardless of whether any action is required. This results in redundant notifications that clutter the inboxes of PR subscribers.
Proposed Solution:
Add an optional parameter, similar to
--github.ScanSubmittedComment=false
, to control the generation of the "Scan Summary & Details" comment in case there are "No policy violation found" and "No package violation found", thereby reducing unnecessary email notifications and improving the user experience.Thank you for considering this enhancement.
The text was updated successfully, but these errors were encountered: