GitHub

Business software

Built when you ask for it

Sync GitHub repositories, issues, pull requests, and commits. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The GitHub connector syncs your repository activity into analytics-ready tables in your data warehouse. Pull repositories, issues, pull requests, reviews, commits, releases, and workflow runs from the GitHub REST API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Repositories
  • Issues and pull requests
  • Reviews and comments
  • Commits and releases
  • Workflow runs

How it gets built

  1. Choose GitHub when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads GitHub's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against GitHub itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

Personal access token or GitHub App. A fine-grained personal access token with read access to the repositories you want, or a GitHub App installation token.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a GitHub connector?
Not as a finished connector yet. Ingest builds it from GitHub's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can GitHub data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

GitHub API documentation: https://docs.github.com/en/rest

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Salesforce, Airtable, Clockify, Facebook Ads.

Request GitHub