Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (actions-usage) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

actions-usage

Show GitHub Actions usage metrics per developer for any repository.

Prerequisites

GitHub CLI (gh) installed and authenticated

Quick Start

npx actions-usage --repo owner/repo

Or run from within a git repo to auto-detect:

npx actions-usage

Options

--repo <owner/repo>   Target repository (default: detect from git remote)
--since <date>        Start date YYYY-MM-DD (default: start of current month)
--until <date>        End date YYYY-MM-DD (default: today)
--format <type>       Output format: table, csv, json (default: table)
--sort <field>        Sort by: minutes, runs, name (default: minutes)
--csv <path>          Export CSV to file
-V, --version         Show version
-h, --help            Show help

Examples

Current month usage:

npx actions-usage --repo my-org/my-repo

Year-to-date:

npx actions-usage --since 2026-01-01

Export to CSV:

npx actions-usage --since 2026-01-01 --csv usage.csv

JSON for piping to other tools:

npx actions-usage --format json | jq '.users[:3]'

How It Works

Queries the GitHub Actions API via gh api to fetch all completed workflow runs in the specified period, then calculates wall-clock duration per developer by measuring the time between run_started_at and updated_at.

Note: These are wall-clock durations, not GitHub billable minutes. The billing API does not expose per-run minutes for private repositories.

License

MIT