DatriseAI-first ETL

GitHub Looker

AI-first ETL from GitHub into Looker. Governed entities, incremental sync, typed landing tables.

How Datrise loads GitHub into Looker

Datrise syncs GitHub's repositories, issues, pull requests, commits, and workflow runs into Looker as governed warehouse tables with LookML-ready naming. Flexible or custom fields land in flattened columns (nested fields expanded for modeling), and timestamps such as created, updated, and status changes are typed as date/time dimension columns.

Sync is incremental: Datrise uses incremental refresh of the underlying warehouse tables Looker explores, so re-runs update only what changed. Date-partitioned fact tables for PDT performance. Looker models live in LookML on top of SQL, so Datrise lands clean, stable column names rather than churn that would break your views.

Ideal for governed, version-controlled BI on a warehouse.

Endpoints

GitHub: Developer platform for repos, issues, and delivery workflows.

Looker: Google Cloud BI with LookML semantic models and governed dashboards.

How GitHub entities map to Looker

GitHub entityLooker objectNotes
repositoriesgithub_repositoriesid PK · custom fields → flattened columns (nested fields expanded for modeling)
issuesgithub_issuesid PK · linked to github_repositories
pull requestsgithub_pull_requestsid PK · linked to github_repositories
commitsgithub_commitsid PK · linked to github_repositories

FAQ

How does Datrise handle GitHub's custom fields in Looker?

Flexible values are stored as flattened columns (nested fields expanded for modeling), so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Looker types.

How does the GitHub to Looker sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the underlying warehouse tables Looker explores.

Related pipelines

Early access

Connect GitHub to Looker the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.