github-actions[bot] opened a new issue, #13879: URL: https://github.com/apache/cloudstack/issues/13879
This issue tracks all runs where threat detection flagged problems in agentic workflows in this repository. Each workflow run that completes with a detection warning or failure posts a comment here. <details> <summary>What is a Detection Problem?</summary> A detection problem occurs when the threat detection system either: - **Detects potential security threats** (prompt injection, secret leak, malicious patch) - **Fails to produce results** (agent failure, parse error) When `continue-on-error: true` (the default), these problems produce warnings and safe outputs still proceed. When `continue-on-error: false`, they block safe outputs entirely. </details> <details> <summary>How This Helps</summary> This issue helps you: - Track workflows where threat detection raised concerns - Review patterns of detection warnings or failures - Identify false positives or recurring issues with threat detection - Monitor the health of the threat detection system </details> <details> <summary>Resources</summary> - [GitHub Agentic Workflows Documentation](https://github.com/github/gh-aw) </details> > [!TIP] > To configure threat detection behavior, update the frontmatter: > ```yaml > safe-outputs: > threat-detection: > continue-on-error: true # Warnings only (default) > # continue-on-error: false # Strict mode — block safe outputs > ``` --- > This issue is automatically managed by GitHub Agentic Workflows. Do not close this issue manually. > > **No action to take** - Do not assign to an agent. <!-- gh-aw-detection-runs --> > - [x] expires <!-- gh-aw-expires: 2026-09-13T14:00:59.779Z --> on Sep 13, 2026, 2:00 PM UTC -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
