bivvy history
Shows the execution history for your project.
Usage
bivvy historyFlags
| Flag | Description |
|---|---|
--limit <N> | Number of runs to show (default: 10) |
--since <duration> | Show runs since a duration ago (supports m, h, d, w suffixes) |
--step <name> | Filter to runs containing the named step |
--detail | Show steps, skipped steps, and errors for each run |
--json | Output as JSON |
Example Output
⛺ Run History
✓ 3 minutes ago default 2 steps 2m 15s ✓ yesterday default 3 steps 5m 30s ✗ 2 days ago ci 1 step 45s ✓ 3 days ago default 2 steps 3m 10sFiltering by Time
Use --since with a duration suffix to show only recent runs:
# Runs in the last hourbivvy history --since 1h
# Runs in the last 7 daysbivvy history --since 7d
# Runs in the last 30 minutesbivvy history --since 30m
# Runs in the last 2 weeksbivvy history --since 2wStep History
Filter to only runs that included a specific step:
bivvy history --step ruby_depsThis shows only runs where the named step was executed or skipped. When combined with --detail, only that step’s information is highlighted in context.
Detailed View
Use --detail to see which steps ran, which were skipped, and any errors:
bivvy history --detail ⛺ Run History
✓ 3 minutes ago default 2 steps 2m 15s Steps: setup, build Skipped: deploy ✗ yesterday ci 1 step 45s Steps: setup Error: build step failedLimiting Results
By default, the last 10 runs are shown. Use --limit to show more:
bivvy history --limit 50JSON Output
Use --json for machine-readable output:
bivvy history --jsonThis outputs the filtered run records as a JSON array, suitable for piping to tools like jq.