combine-gh-stats

Generate a single GitHub-style contribution heatmap SVG and an activity overview SVG from multiple accounts, and keep them up to date with GitHub Actions.

What this repo includes

• scripts/generate-combined-svg.mjs queries GitHub's GraphQL API, merges daily contribution counts, and renders two SVGs: combined-contributions.svg (the heatmap) and combined-activity-overview.svg (the activity overview)
• .github/workflows/update-combined-graph.yml regenerates the SVGs every day and commits changes back to the repo
• fixtures/mock-contributions.json gives you a local mock dataset so you can verify the renderer without a live token

Quick start

1. Create a repository and add these files.
2. Add a repository variable named USERS with a comma-separated list such as account1,account2.
3. The workflow uses GitHub Actions' built-in GITHUB_TOKEN; only this shared token is used for all accounts.
4. Run the workflow once with Actions -> Update Combined Graph -> Run workflow.
5. Embed the generated SVGs in your profile README:

![Combined Contributions](https://raw.githubusercontent.com/USER/REPO/main/combined-contributions.svg)
![Combined Activity Overview](https://raw.githubusercontent.com/USER/REPO/main/combined-activity-overview.svg)

If you are using this in the same repository where the SVG is generated, you can also use:

![Combined Contributions](./combined-contributions.svg)
![Combined Activity Overview](./combined-activity-overview.svg)

Local usage

Create a local .env file:

USERS=account1,account2
GITHUB_TOKEN=ghp_xxx

Then generate the SVGs:

npm run generate

npm run generate now loads .env automatically when the file exists.

Generate with mock data:

npm run verify:mock

The mock command writes sample SVGs to tmp/combined-contributions.svg and tmp/combined-activity-overview.svg.

Run the test suite:

npm test

npm test runs the Node test suite (node --test).

Tokens

The workflow uses GitHub Actions' built-in GITHUB_TOKEN, and local runs use GITHUB_TOKEN from .env. Only this single shared token is used for all accounts.

When GitHub reports private contributions in the selected window, the activity overview's accessible description notes that GitHub does not break those contributions down into commits, PRs, issues, and reviews.

Customization

• OUTPUT_FILE changes the destination heatmap SVG path
• TITLE changes the heading shown inside the heatmap SVG
• DAYS changes how many trailing days to include; default is 365
• OVERVIEW_OUTPUT_FILE changes the destination activity overview SVG path
• OVERVIEW_TITLE changes the heading shown inside the activity overview SVG
• MAX_REPOSITORIES caps the number of repositories queried per account
• MAX_QUERY_DAYS caps the number of days each GraphQL query window can span
• MOCK_DATA_FILE points the renderer at a local JSON fixture instead of the live API

The generated SVGs also adapt to light and dark mode automatically with prefers-color-scheme.

Rate limits

GitHub's GraphQL API enforces a shared rate-limit budget (points per hour) across all queries. Each account in USERS adds queries, so a large USERS list can exhaust the GraphQL budget before every account is fetched. To stay within limits, reduce the number of accounts, lower DAYS to shrink the query window, or lower MAX_QUERY_DAYS to keep individual queries small.

Notes

• GitHub's native contribution graph cannot be merged across accounts; this generates separate SVGs for display.
• The README images will appear after the first successful workflow run creates combined-contributions.svg and combined-activity-overview.svg.