Compact, zero-framework HTML/CSS/JS dashboard for viewing recent commits across any mix of GitHub orgs, user accounts, and individual owner/repo repositories. Fetches directly in the browser via GitHub GraphQL and caches results in localStorage.
Click the top-left target badge (e.g. nais ▾), click Configure, or press s:
- Targets: comma/newline-separated orgs, users, or specific repos (e.g.
nais, sechmann, navikt/naisdevice). - Branch scope: Default branch (
main/master) or All branches (scans active branches and dedupes by commit SHA). - GitHub Token: click Create read-only token on GitHub ↗ to create a fine-grained personal access token, then paste it (stored in a browser cookie +
localStorage). The link pre-selects the permissions below and, when all targets share one owner, that resource owner.
Create a read-only PAT with:
- Contents: Read-only — commit history, branches, and commit statistics.
- Pull requests: Read-only — associated pull request details.
- Metadata: Read-only — included automatically; no organization-level permissions needed.
Choose the Resource owner and Only select repositories to limit access to the repositories you need. The link defaults to a 30-day expiration. Organizations may require approval or restrict PAT access.
A fine-grained PAT grants private repository access under only one resource owner; it cannot cover private repos across multiple owners, and outside-collaborator access has limitations. Public repositories remain readable. Narrow your targets if needed rather than granting the broad read/write repo scope of a classic PAT. See GitHub's PAT documentation for current limitations.
Create config.local.js using the read-only PAT above:
window.NAIS_DASH_CONFIG = {
targets: "nais",
branchMode: "default",
token: "github_pat_REPLACE_WITH_YOUR_READ_ONLY_TOKEN",
};Keep this file private. It is gitignored, but any web server serving the dashboard can also serve this file; never deploy it with a real token.
python3 -m http.server 8000Authenticated dashboards automatically refresh every 60 seconds while the tab is visible and the browser is online. Polling pauses while configuration is open, never overlaps another fetch, and backs off after failures (up to 15 minutes). Returning to a visible/online tab runs an overdue refresh.
Between full reconciliations:
- Repository listings stop once push timestamps are older than the last successful fetch, with a five-minute overlap. Older cached repositories are retained.
- Unchanged branch heads skip commit-history queries. Changed repositories query commits since that same recent cutoff and merge them by repository + SHA.
- New repositories, changed default branches, and added/deleted branches get a full history fetch immediately when detected.
- Cached commits outside the rolling time window are removed. Failed fetches leave the last successful snapshot and cutoff unchanged.
Every 15 minutes, the next refresh reconciles the entire selected time window, replacing cached history and updating PR details. Commit dates are not push dates: backdated commits, force-push removals, and repositories removed from account listings can remain missing or stale until reconciliation. A wider time window or an older cache also triggers a full fetch.
Snapshots persist in localStorage, so they survive page reloads. Configure autoRefreshSeconds (default 60, minimum 15, or 0 to disable) and cacheTtlMinutes (default 15, reconciliation interval) in config.local.js. The Refresh button and r use the same incremental/reconciliation logic. Unauthenticated public preview remains manual and fetches its data afresh.
/— focus filter (Escclears)r— refresh commits from GitHubs— open target / branch / token configuration- URL params:
?targets=nais,sechmann&branches=all&days=7 - Filter qualifiers:
repo:cli,owner:nais,branch:feat,author:vegar,pr:123,sha:a1b2c3,is:bot,is:human,is:pr