Asking my CI "why did that fail?": GitHub Actions cognee
说明与用途
作者为 cognee 构建了 GitHub Actions 连接器,以获取 CI 运行数据、裁剪日志并将其存储为文档,从而使 LLM 能够跨多次运行查询失败原因和修复方案。
问题
CI history is hard to query; finding why runs fail requires manual log inspection and is not searchable across runs.
结果
The demo ingested 15 runs in 8.2 s, built embeddings in 105.3 s, and answered three questions: list recent failures and reasons, how to fix a specific failure, and which runs are waiting for approval.
工作流
- 1. Use github_actions_source() to pull recent runs from a repo
- 2. Ingest the source into cognee with cognee.remember()
- 3. Query the memory with natural language questions
证据
I wanted to ask my CI a plain question: "which workflows failed recently, and why?"
The connector is a single function, github_actions_source(). You give it one or more owner/repo names, and it returns a dlt source that cognee can ingest directly.
The connector pulled 15 runs, their jobs, and the logs of the failed jobs in 8.2 s. Only 3 had actually failed. 10 were waiting for approval.
Add the COGNEE_BUMP_PR_TOKEN secret to the repository's GitHub Actions secrets (see the workflow header for details), then rerun the scheduled workflow.
- 记录日期: 2026-11-02T01:59:17.274Z