Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[aw] Detection Runs

未關閉
#22,642 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
10/100
Issue 類型
文件
描述清晰度
描述清楚
活躍度
活躍
領域
devops, security

研究方向

This is an automated tracking issue for threat detection runs in agentic workflows. It is not a task for a contributor; the issue explicitly states 'No action to take' and 'Do not assign to an agent.' The comments will contain logs of detection warnings or failures for review by maintainers.

由索引模型根據 Issue 內容生成。

描述

agentic-workflows

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.

What is a Detection Problem?

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.

How This Helps

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
Resources

[!TIP]
To configure threat detection behavior, update the frontmatter:

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.

  • expires on Oct 22, 2026, 8:42 AM UTC
主要語言
CodeQL
星號
10.1k
分支
2.1k
平均合併
2 天 16 小時
30 天內合併 PR
143

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

github/codeql 的其他 Issue

查看 github/codeql 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。