Details:

Allow users to configure which jobs trigger Slack failure notifications. Today, any job failure in a workflow fires a notification — with no way to distinguish between a critical test suite failure and a known-noisy ancillary job (e.g., a code coverage metrics job that flakes on dependency issues).

Teams with complex workflows are getting paged on failures they don't care about, leading to alert fatigue and, in some cases, disabling the integration entirely.

Proposed behavior:

Users can exclude specific jobs from triggering failure notifications, either by job name or by marking them as non-blocking for notification purposes. This could be implemented as a job-level toggle in the Slack notification settings UI, or as a filter list (similar to branch filtering).

Why this matters:

The inability to filter at the job level is one of the top drivers of notification noise for teams with multi-job workflows. Without this, the integration is all-or-nothing — teams get notified on all workflow failures or turn it off.