Skip to main content

Troubleshooting

Pages workflow fails on initial commit​

If setup-node fails with "Some specified paths were not resolved, unable to cache dependencies", the history repo is missing web/package-lock.json and the vendored @actions-insights/history-models package.

See Fixing an already-created history repository in the deployment guide.

node_modules committed to git​

If web/node_modules/ was committed (for example before .gitignore was added), remove it from version control:

cp /path/to/actions-insights/templates/history-repo/.gitignore .gitignore
git rm -r --cached web/node_modules
git commit -m "Stop tracking web/node_modules"
git push

Or run bash scripts/update-history-repo.sh update <owner>/<history-repo> from an actions-insights checkout to open a PR with the fix.

History publish skipped​

  • Verify history-enabled: true
  • Ensure history-repository is set
  • Ensure history-token secret is configured and has contents: write

Push conflicts​

Multiple workflows pushing simultaneously may conflict on index files. The action retries up to 3 times with rebase. If failures persist:

  • Reduce concurrent writes to the same branch
  • Check history repo branch protection rules allow pushes

Dashboard 404​

  • Confirm GitHub Pages is enabled (Actions source)
  • Check the Pages workflow completed successfully
  • Verify VITE_BASE_PATH matches your Pages URL (/{repo-name}/ for project pages)

The dashboard uses hash-based URLs (for example .../repo-name/#/r/owner.repo/b/main/run/1). Path-based URLs without the # (for example .../repo-name/r/owner.repo/...) will not work on GitHub Pages.

If you have an older dashboard build that used path-based routing, run bash scripts/update-history-repo.sh update <owner>/<history-repo> to pick up hash routing.

Blank page after dashboard update​

The dashboard uses HashRouter for GitHub Pages. Do not set basename on HashRouter — unlike BrowserRouter, it applies to the hash segment, not the repo path, and causes the router to match no routes. VITE_BASE_PATH is only for static assets and data fetches (import.meta.env.BASE_URL).

If the site is blank after updating, run bash scripts/update-history-repo.sh update <owner>/<history-repo> to pick up the latest dashboard build.

Empty repository list​

  • Confirm the action has published at least one run
  • Check data/repositories.json exists in the history repo
  • Verify JSON was copied into the Pages deploy artifact

Token permission errors​

The history-token must have write access to the history repository, not just the source repository.