🔐 Workflows Updates: Exclude Repos, More Webhook Trigger Conditions, and Build Scan Enhancements
New improvements are now live in Workflows:
Exclude repos, applications, or teams from a workflow
Workflows can now be scoped to exclude specific repositories, applications, or teams. If a workflow is triggering on scope you don't want it to act on, you can exclude that scope directly instead of rebuilding the workflow's conditions.
Send a webhook on risk added / risk resolved
You can now send a webhook from workflows triggered by a risk added or risk resolved condition. Webhooks were already supported for other trigger conditions - this closes the gap for these two.
More Control Over Build Scan Workflows
You can now add policy tags to Build Scan workflows, matching the tag-based scoping already available for Diff Scan and Risk Added workflows.
You can now trigger workflow actions on a Build Failure - not just fail the build, but run whatever action you configure (e.g. notify a channel, create a ticket).
You can now scope a Build Scan workflow to a specific application or team, instead of it running across everything.