Skip to content

[deep-report] daily-secrets-analysis workflow is missing cache-memory, blocking its own trend-tracking recommendation #64554

Description

@github-actions

Description

.github/workflows/daily-secrets-analysis.md has no cache-memory tool configured (confirmed via direct read — no cache-memory key anywhere in its frontmatter). Its own generated report explicitly recommends "Persist daily stats (e.g. cache-memory) to enable trend comparison; none was available today," but the workflow can't act on that recommendation without the config. Other workflows in this repo (e.g. cli-version-checker.md) already use the simple cache-memory: true form successfully.

Add cache-memory: true to the workflow's tools: block, and add a short step in the prompt instructing the agent to write that day's summary metrics (total secrets references, unique secret types, redaction/permission-block counts) to /tmp/gh-aw/cache-memory/ and read the prior day's file back for a day-over-day trend line in the report.

Expected Impact

Turns a currently point-in-time daily report into a trend-tracking one, matching the pattern already used by several sibling daily-audit workflows — lets future runs flag actual regressions (e.g. a sudden drop in redaction coverage) instead of only reporting the current snapshot.

Suggested Agent

GitHub Copilot coding agent (workflow frontmatter + prompt edit, then make recompile).

Estimated Effort

Quick (< 1 hour)

Data Source

DeepReport Intelligence Briefing — 2026-09-30, sourced from Daily Secrets Analysis Report #64547, root-caused by direct read of the workflow's frontmatter.

Generated by 🔬 Deep Report · claude · agent · 311.3 AIC · ⌖ 8.86 AIC · ⊞ 7.3K · ◷

  • expires on Oct 2, 2026, 10:46 AM UTC-08:00

Activity

  1. github-actions commented on Oct 2, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-02T18:46:27.941Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions