Skip to content

v1.2.3

Latest

Choose a tag to compare

@github-actions github-actions released this 06 Aug 04:14
· 1 commit to master since this release

Added

  • Optional USD/CNY cost estimates. Reports can convert AI credits using GitHub's official 1 credit = $0.01 USD rate and an editable USD→CNY rate, defaulting to 6.75 with a 2026-08-06 reference date. Cost display is off by default, with direct links to GitHub billing, official documentation, and UsagePricing.
  • Quick date ranges. Choose the last 7 days, 30 days, 3 months, or all data (the default) while retaining custom start/end dates.

Fixed

  • Daily machine bars now follow the selected date range. Date shortcuts and custom dates update the stacked daily chart together with the rest of the report.
  • Repeated VS Code session snapshots are no longer double-counted. The scanner keeps the latest persisted state for each stable response ID, preventing append-style JSONL rewrites from inflating credits and turn counts; merged CSV reports continue to deduplicate matching records across machines.
  • Copilot CLI sessions now appear in reports. The scanner uses each session's events.jsonl as the traceable source record, workspace.yaml.name as the authoritative title (falling back to the first real user message), and workspace.yaml.cwd for the project. Only after a SQLite usage row matches a JSONL response does session-store.db enrich it with precise nano-AIU credits, duration, and turn metadata.
  • Active and legacy CLI sessions are both covered. Current usage is enriched from SQLite (including its live WAL); older sessions absent from the usage table are recovered from non-zero session.shutdown metrics without double counting.
  • CLI sources open at the matching event. Every correlated record points to its real events.jsonl response line, and the report's Open action launches that exact line in VS Code instead of opening the SQLite database.

Changed

  • Copilot CLI scanning is enabled by default. A normal gh-usage run now combines VS Code and CLI usage automatically. Use --no-cli-logs when you explicitly want a VS Code-only report. The old --include-cli-logs flag remains accepted for compatibility.