GitHub

Renta exports GitHub data to your data warehouse: commits, issues, pull requests, releases, GitHub Actions runs, and other repository objects. The full list is in the Report type section.

You pick the repositories and the fields of each object yourself.

Authentication

Renta connects to GitHub through OAuth. You log in to GitHub, confirm the access Renta asks for, and return to Renta. You do not need to create a personal access token.

On the consent screen, GitHub asks for access that covers everything Renta can export:

1. Repositories.
   Code, branches, commits, issues, and pull requests, including private repositories.
2. GitHub Actions.
   Workflows, their runs, and jobs.
3. Organization.
   Teams and their members.
4. Profile.
   The login and email of the connected account.

GitHub has no read-only version of the repository and workflow access, so the consent screen mentions write access. Renta only reads data.

Connect GitHub source

Follow these steps to add GitHub as a source in Renta by authorizing access to your GitHub account.

Go to the CatalogStep 1

1. Navigate to the Connections > Catalog section in the left sidebar.
2. Open the Developer tools category and click the GitHub card.

Authorize connectionStep 2

Click Log in to your GitHub account. Renta redirects you to GitHub, where you sign in and confirm the access it requests. If the browser already holds an authorized GitHub session, the confirmation goes through right away and you return to Renta.

Name the connection and saveStep 3

Finish the setup:

1. Source name.
   Specify a name for this data source. It is used exclusively in the Renta interface.
2. Access granted.
   Verify that the account is connected. The card carries the login of the authorized GitHub account.

Click Save to finish.

If the authorization later changes, for example after you revoke the app in GitHub, click Re-authorize on this source. The connection refreshes in place and every pipeline built on it keeps running.

Source createdStep 4

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Create a pipeline

Once the source is connected, create a pipeline to sync your GitHub data into your destination.

Create a GitHub pipeline

Link your GitHub source to a destination and configure the pipeline.

Select GitHub as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select GitHub under Already connected and click Next step.

Select your GitHub connectionStep 2

Choose the GitHub connection you created earlier and click Next step. The card shows the account behind the connection and the date it was added.

Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step. The card shows the dataset and project the data will land in.

Pipeline configuration

On the final step, choose which GitHub data to export, from which repositories, and how often Renta loads it.

Integration type

Choose how to configure the pipeline: assemble one report yourself or start from a template.

A template creates one pipeline per report type it covers, so one Create pipeline click can produce more than a dozen pipelines. Renta offers five templates: repository basics, issues and pull requests, CI/CD, organization, and all objects.

Report type

Select which GitHub object the pipeline exports. One pipeline loads one report type.

Repositories

Select the repositories the pipeline reads.

The picker lists every repository the authorized account can reach, with the owner/repo name under each title. Use the search field to find a repository by name, or click Select All. The Selected tab shows what you picked, and the Selected Repositories list below the picker lets you remove an entry.

The Repositories report type has no repository picker: it always returns every repository the account can reach.

Teams and Team Members are organization objects. Renta takes the organization from the owner of each selected repository, so a repository owned by a personal account contributes nothing to these two reports.

Parameters

Select the GitHub fields to include in the destination table. Your dataset schema is defined by the parameters you choose here.

Every row shows the field name with the destination column name below it: Node ID becomes the node_id column. Use the search to find a field by name, review the choice on the Selected tab, and remove a field from the Selected Parameters list below the picker.

The set of available fields depends on the report type. Renta flattens the objects GitHub nests inside a record, so the author of a commit arrives as Author Login, Author ID, Author Type, and Author HTML URL, and the milestone of a pull request as Milestone ID, Milestone Title, Milestone State, and Milestone Due On.

Fields that hold a list of objects load as nested records.

Fields whose shape depends on the record itself arrive as JSON. These are Payload in Events and Deployments, Reactions wherever GitHub reports them, Auto Merge, Head Repo, and Base Repo in the pull request reports, Repository, Head Repository, and Referenced Workflows in Workflow Runs, and the entity fields of Issue Events such as Label, Assignee, Milestone, and Rename.

Table name

Name the pipeline and the destination table.

1. Integration name.
   The name of the pipeline. It is used exclusively in the Renta interface.
2. Table name.
   The destination table name. You can keep the auto-generated name or enter your own.

Date range

Set the historical period to load. By default, Date start is the first day of the current month and Date end is Today.

1. Date start.
   The first date of the extraction period.
2. Date end.
   The last date of the extraction period. You can pick a fixed date or a relative option such as Today.

Renta keeps only the records whose date falls inside the range. A repository nobody updated within the range does not reach the Repositories table, and neither does a pull request untouched since last year. Set Date start far enough back for the history you need.

Branches, Tags, Issue Labels, Pull Request Commits, Collaborators, Assignees, Teams, and Team Members carry no date, so they ignore the range and load in full.

Overwrite period

The overwrite period defines how many recent days Renta reloads on every run. Renta pre-selects the date parameter the report type is partitioned by, so the setting is visible for every report type in the table below.

On each run, Renta re-fetches the data starting from the date of the last successful run minus the overwrite period. The affected days are deleted from the destination table and inserted again, while older data stays untouched.

The options range from Without overwrite data to Overwrite all data. The default is Last 1 day.

Schedule

Choose how often the pipeline runs.

For Daily schedules, set the Update time, the exact time each run starts, then click Create pipeline.

The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Limitations

The GitHub API sets boundaries that apply to every pipeline built on this source.

Sync strategy

How Renta synchronizes a GitHub report depends on the report type and on whether the destination supports merge.