Connector

Collect GitHub data in Google BigQuery

Load repository details, contributors and daily star counts from GitHub into your own BigQuery dataset with OWOX Data Marts, then query engineering activity next to the product and revenue tables you already keep there.

GitHubConnectedRepository Contr…Repository Infor…Repository Stati…
Data MartPublishedone definition
Google BigQueryLoginIdNodeDaily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get started free

Hand this to your AI

GitHub shows today's star count, not its history, so last quarter's growth is a guess.

Paste this into your AI assistant. It loads GitHub repository statistics into your Google BigQuery dataset daily with OWOX Data Marts, so a star and contributor history builds up from the first run.

The prompt

load GitHub repository statistics into Google BigQuery every day and build a history of stars and contributors per repository, with the change by month and by week

Endpoints

S00 · Why

Why GitHub data belongs next to your product and revenue tables

Stars, forks and contributors say how alive a project is. They say more when they sit beside sign-ups and revenue in the same data warehouse: you can ask what changed on the day a release shipped, in one BigQuery query.

  • Line up daily stars with sign-ups in one BigQuery query
  • Keep a daily star count that GitHub's repository page does not show
  • Report engineering activity next to revenue without a spreadsheet in between
GitHubRepository activity
Product analy…Sign-ups by day
RevenueOrders and invoices
Your data warehouseBigQueryRepositorySign-upsRevenueJoined by idYour release dateSign-ups and revenue afterOne BigQuery query lines up the release date with what came next.

S01 · Step 1

Step 1: Connect GitHub and pick the fields

Create a Data Mart, choose GitHub as the data source, enter the repository as owner/repo, add an access token and tick the fields you need.

  • Three endpoints: Repository Information, Repository Contributors and Repository Statistics
  • Authentication is by access token, which you paste once
New Data MartChoose a sourceGoogle AdsGitHubFacebook AdsAuthorizeConnectedEndpointRepository Inform…Repository Contri…Repository Statis…
Repository Inform…42 fieldsfull_namestargazers_countforks_countopen_issues_countlanguagepushed_at

S02 · Step 2

Step 2: Load GitHub into a BigQuery table

Pick the dataset and table in your data storage; the names are pre-filled and you can change them. Run it and the first load lands in your own BigQuery project.

  • The tables are github_repository, github_contributors and github_repository_stats
  • The statistics table is partitioned by date, one row per day, so a date filter scans only that period
DestinationBigQueryDatasetgithubTablerepositoryRun
Run HistoryPendingRunningSuccessIncremental load
Tablegithub.repository

S03 · Step 3

Step 3: Get a readable output schema

After the first run you get the output schema: every field with a plain description. Your data quality checks can read it too.

  • full_name is the owner and repository, stargazers_count a number, pushed_at a date
  • date is a DATE column, and the statistics table is partitioned on it
github.repositoryOutput schemaFieldDescriptionfull_nameFull repository name (owner/repo)stargazers_countNumber of starsforks_countNumber of forksopen_issues_countNumber of open issueslanguagePrimary programming languagepushed_atRepository last push date

S05 · Step 5

Step 5: Schedule the refresh and start the history

Set it once. A scheduled refresh adds today's row to the statistics table and updates the repository and contributor rows in your Google BigQuery tables.

  • Run it daily so the statistics table, partitioned by date, gets a row for every day
  • GitHub returns today's counts only, so there is nothing to backfill: your BigQuery history starts with the first run
ScheduleRun on a scheduleDaily 09:00
BackfillRun backfill
Run HistoryDaily scheduleManual backfillDaily schedule

S06 · Step 6

Step 6: Reuse the same BigQuery tables everywhere

One set of tables feeds your data model, spreadsheets, dashboards, AI assistants like Claude and ChatGPT, and scheduled AI insights in Slack or email.

  • Every report reads the same numbers, so the totals agree
  • Ask an AI assistant how many stars the repository gained last month, from your BigQuery tables
GitHubData MartPublished
Engineering activity…
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email

Recent updates

Why OWOX

Why OWOX for GitHub data in BigQuery

A script that calls the GitHub API, or a weekly export to a spreadsheet, gets you numbers. OWOX keeps them in the Google BigQuery tables where your product and revenue data already are.

  • You own the data. The data lands in your own BigQuery project, in tables you control and can join to anything.
  • History you keep. GitHub's repository page shows the current count. In BigQuery the statistics table adds a row for every day you run it, so the trend stays.
  • Ready for a data model. full_name and date are the join columns, so releases and sign-ups are one line in your model.
  • Maintained for you. No script to fix when the GitHub API changes.

Book a callGet started free

Trust

The Data Partner You Can Trust

users

175K Source: Internal OWOX data as of 2026-11-11

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

171K3

In Open Source We Trust

Customers