History Repository

The history repository is an optional feature that pushes structured JSON test data to a separate git repository. A React dashboard hosted on GitHub Pages presents test results for all branches and repositories in a beautiful, responsive interface.

When to Enable

Enable the history repository when you need:

• Org-wide visibility across multiple repositories
• Persistent history that survives workflow artifact expiry
• A hosted dashboard on GitHub Pages for all branches
• Trend analysis and stability metrics over time

For single-repo setups with per-run investigation, the HTML artifact may be sufficient.

How It Works

1. Actions Insights pushes structured JSON after each test run
2. The history repository stores data under data/
3. A GitHub Actions workflow builds and deploys the React dashboard to GitHub Pages

Minimal Configuration

- uses: mzbrau/actions-insights@v1
  with:
    test-results: '**/*.trx'
    history-enabled: true
    history-repository: 'my-org/actions-insights-history'
    history-token: ${{ secrets.HISTORY_REPO_TOKEN }}

Setup Steps

The history repository requires a one-time setup:

1. Deploy the history repository — run the init script or use the gh extension
2. Configure secrets — create a token with write access
3. Enable in your workflow — set history-enabled: true and the inputs above

Key Inputs

Input	Default	Description
history-enabled	false	Enable JSON publishing
history-repository	''	History repo (owner/repo)
history-token	''	Token with write access
history-branch	main	Target branch
history-path	data	Data root path

Learn More

• History Repository Deployment — init script, GitHub Pages setup
• History Repository Configuration — full input reference
• Adding Repositories — multi-repo setup
• Import Historical Data — backfill from workflow artifacts
• Troubleshooting — common issues