From f20764df9eda687e333d08b72ae6618a03176e4d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jakob=20M=C3=B6ller?= <jakob.moeller@sap.com>
Date: Tue, 19 Nov 2024 11:33:59 +0100
Subject: [PATCH] chore: allow triggering blackduck scans manually (#1104)

<!-- markdownlint-disable MD041 -->
#### What this PR does / why we need it

it is currently impossible to trigger the blackduck scans manually so
now we should be able to in case we have a transient failure.

#### Which issue(s) this PR fixes
<!--
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
---
 .github/workflows/blackduck_scan_scheduled.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/workflows/blackduck_scan_scheduled.yaml b/.github/workflows/blackduck_scan_scheduled.yaml
index 9491840c0d..4622f7c5e9 100644
--- a/.github/workflows/blackduck_scan_scheduled.yaml
+++ b/.github/workflows/blackduck_scan_scheduled.yaml
@@ -2,6 +2,7 @@ name: Blackduck Scan Cronjob
 on:
   schedule:
     - cron:  '5 0 * * 0'
+  workflow_dispatch:
   
 permissions:
   checks: write