Add on-demand token audit workflow with date-range dispatch input#36412
Conversation
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
|
@copilot Revert changes to |
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Fixed in commit |
There was a problem hiding this comment.
Pull request overview
Adds a new on-demand “Agentic Workflow Token Trend Audit” workflow that can be manually dispatched with a caller-provided date range, downloads gh aw logs JSON for that window, and prompts an agent to persist snapshots, generate charts, and publish an issue emphasizing the historical token trend.
Changes:
- Introduces
.github/workflows/agentic-token-trend-audit.mdwithworkflow_dispatchinputdate_rangeand dynamic--start-date/--end-datelog collection. - Adds instructions to persist snapshot + rolling summary, generate token charts, and publish an audit issue focused on the trend chart.
- Commits the compiled workflow lock file
.github/workflows/agentic-token-trend-audit.lock.yml.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/agentic-token-trend-audit.md |
New on-demand token trend audit workflow definition, including date-range input parsing and agent instructions for snapshots/charts/issue publication. |
.github/workflows/agentic-token-trend-audit.lock.yml |
Compiled lockfile for the new workflow (runtime-executed GitHub Actions YAML). |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/2 changed files
- Comments generated: 4
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
|
|
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
|
@copilot Recompile workflows |
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
This change introduces an on-demand variant of the Agentic Token Audit that runs via
workflow_dispatchand accepts a caller-provided date range for analysis.Scope of change
.github/workflows/agentic-token-trend-audit.md.github/workflows/agentic-token-trend-audit.lock.ymlTrigger and input model
workflow_dispatchinput:date_range(default:-30d..-0d)<start>..<end>(e.g.,2026-05-01..2026-05-31)Date-range log collection
date_range.--start-date -1dto dynamic:--start-date "$START_DATE"--end-date "$END_DATE"