Skip to content

fix(api-consumption-report): enable cache-memory to persist trending history#29055

Merged
pelikhan merged 2 commits into
mainfrom
copilot/fix-cache-memory-trending-history
Apr 29, 2026
Merged

fix(api-consumption-report): enable cache-memory to persist trending history#29055
pelikhan merged 2 commits into
mainfrom
copilot/fix-cache-memory-trending-history

Conversation

Copilot AI commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

cache-memory was missing from the workflow's tools frontmatter, so the trending history file (/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl) was discarded after every run — every execution saw "first run", and multi-day trend charts had only a single data point.

Changes

  • .github/workflows/api-consumption-report.md: Added cache-memory: true to tools
tools:
  cache-memory: true   # ← added
  cli-proxy: true
  agentic-workflows:
  • .github/workflows/api-consumption-report.lock.yml: Recompiled to include cache-memory setup/restore/commit steps

Copilot AI changed the title [WIP] Fix api-consumption-report to enable cache-memory for trending history fix(api-consumption-report): enable cache-memory to persist trending history Apr 29, 2026
Copilot AI requested a review from pelikhan April 29, 2026 05:24
@pelikhan pelikhan marked this pull request as ready for review April 29, 2026 05:29
Copilot AI review requested due to automatic review settings April 29, 2026 05:29
@pelikhan pelikhan merged commit c5224f7 into main Apr 29, 2026
20 checks passed
@pelikhan pelikhan deleted the copilot/fix-cache-memory-trending-history branch April 29, 2026 05:29

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Enables cache-memory for the api-consumption-report agentic workflow so its trending history under /tmp/gh-aw/cache-memory/... persists across runs and multi-day charts can accumulate data points.

Changes:

  • Added cache-memory: true to the workflow frontmatter tools configuration.
  • Recompiled the generated lock workflow to include cache-memory restore/setup/save steps (and updated associated generated identifiers).
Show a summary per file
File Description
.github/workflows/api-consumption-report.md Enables the cache-memory tool in frontmatter so the workflow can persist trending history across runs.
.github/workflows/api-consumption-report.lock.yml Updates the compiled workflow to restore/setup and save the cache-memory directory via actions/cache.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 2/2 changed files
  • Comments generated: 0

@github-actions github-actions Bot mentioned this pull request Apr 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[q] fix(api-consumption-report): enable cache-memory to persist trending history

3 participants