Balloon Popups vs. Event Log for VCS Notification Noise

WebStorm provides granular control over IDE events via Settings | Appearance & Behavior | Notifications. Developers can route specific notification groups, such as Version Control (VCS), through either transient balloon popups or the persistent Event Log tool window.

The goal is to minimize visual interruptions during active coding sessions while ensuring that critical failures—such as failed pushes or merge conflicts—are not missed. Balloon notifications provide immediate visibility but can be intrusive, whereas the Event Log captures all history silently without stealing focus.

When configuring VCS operation results, there is a trade-off between immediate awareness and a distraction-free environment. Demoting these alerts to log-only reduces noise but removes the visual cue that a background process has failed.

• Is it more effective to keep VCS notifications as balloons and rely on system-level "Do Not Disturb" modes, or to demote them to the Event Log and implement a manual check routine?
• Does WebStorm offer a way to trigger a balloon only on failure while keeping successful operations log-only within the same notification group?