Actions Hub — GitHub Actions Dashboard

All your GitHub Actions workflow runs in one dashboard: filters, favorites, search and build-failure notifications.

Actions Hub gathers the GitHub Actions workflow runs from every repository you care about into a single dashboard — so you stop opening the Actions tab of one repo at a time to find out what broke. WHAT IT DOES • One view of everything running, queued, failing or passing across your organization and your personal repositories. • Filters by status, repository and workflow. Click to focus on one, Cmd/Ctrl + click to select several. • Favorites — star the repositories and workflows that matter. They move to the top of the lists, and you can limit notifications to them alone. • Instant search across repo, workflow, branch, commit message, author, SHA, event and run number. • Desktop notifications when a build breaks, and optionally when it goes back to green. Click one to jump straight to the run on GitHub. • A badge on the toolbar icon: red with the number of new failures, yellow with the number of runs currently active. • Quick actions from the list itself — re-run the failed jobs, cancel a run in progress, or open it on GitHub. • A compact popup with the summary and whatever needs attention right now. • Light and dark themes, following your system by default. HOW IT WORKS You create a GitHub Personal Access Token, paste it into the settings, and pick which repositories to watch — or let the extension track your most recently pushed ones automatically. From then on it checks the GitHub API on the interval you choose (2 minutes by default). Every response is cached with its ETag, so the next request is conditional and GitHub answers "304 Not Modified" whenever nothing changed. Those responses do not count against your rate limit, which is why watching 30 repositories every 2 minutes costs a small fraction of the 5,000 requests per hour you get. The budget left is shown in the corner of the dashboard. PRIVACY Actions Hub has no backend. There is no server run by the developer, no analytics and no telemetry, and no third party receives anything. Your token, your preferences and the cached runs live in your browser's local storage and nowhere else. The only host the extension is allowed to contact is api.github.com — it requests no other host permission and injects no content script, so it never sees the pages you browse. "Erase all data" in the settings removes everything, and uninstalling the extension deletes its storage. Full policy: https://github.com/danpalmieri/actions-hub-chrome-extension/blob/main/PRIVACY.md WHAT YOU NEED A GitHub Personal Access Token (classic) with the "repo" scope — or just "public_repo" if you only watch public repositories. For fine-grained tokens, grant "Actions: read", plus write if you want the re-run and cancel buttons. If your organization uses SAML SSO, authorize the token for that organization on GitHub, otherwise its private repositories answer 403. OPEN SOURCE The full source is on GitHub under the MIT license — no build step, no bundler, no minified code: https://github.com/danpalmieri/actions-hub-chrome-extension