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 摘要。