GitHub Release Notes

October 2021link

We have added a new table, COMMIT_PULL_REQUEST. This table stores linking information between commits and their relevant pull requests. We are gradually rolling out this feature to all existing connectors. Once it’s available for your connector you will see the table in your destination. To get the data for all commits, re-sync your connector.

We have added two new tables:

• DEPLOYMENT stores deployment information
• DEPLOYMENT_STATUS stores deployment status information We are gradually rolling out this feature to all existing connectors. Once it is available for your connector, you will be able to manage syncing of these tables on the Schema tab of your Fivetran dashboard.

We have added two new tables:

• RELEASE stores release information
• ASSET stores asset information We are gradually rolling out this feature to all existing connectors. Once it is available for your connector, you will be able to manage syncing of these tables on the Schema tab of your Fivetran dashboard.

April 2021link

We have added a new table, LABEL. We have deprecated the label column and added a new column, label_id, to the following tables:

• ISSUE_LABEL
• ISSUE_LABEL_HISTORY

This feature applies to all GitHub connections set up after April 19, 2021. See the GitHub Schema Information section for details.

February 2021link

We can now sync commits from deleted branches that were associated with pull requests. We are gradually rolling out this improvement to all existing customers. If you have missing commits in your destination, re-sync your connector.

December 2020link

We have added a new field, draft, to the PULL_REQUEST table. The draft field indicates whether the pull request is a draft.

August 2020link

We have released a pre-built dbt package for GitHub. Find the package in Fivetran’s dbt hub. Learn more about our dbt integration in our dbt Transformations documentation.

May 2020link

You can now configure your GitHub connector using the Fivetran REST API. This feature is in BETA and available only for Standard and Enterprise accounts.

September 2019link

We now support Teams in our GitHub connector. We have added three new tables:

• TEAM to collect information about organization teams
• TEAM_MEMBERSHIP to store team membership data
• REPO_TEAM to keep the relationship between team and repo, including team permission level

June 2019link

• We now use the GitHub Webhook API. It allows us to make incremental updates faster and capture deletes for the following tables:

  • MILESTONE
  • PROJECT
  • COLUMN
  • CARD

• We now support Projects in our GitHub connector. We have added four new tables:

  • PROJECT table with the fields:

    • id
    • repository_id
    • creator_id
    • body
    • number
    • state
    • name
    • created_at
    • updated_at
    • is_deleted

  • COLUMN table with the fields:

    • id
    • project_id
    • name
    • created_at
    • updated_at
    • is_deleted

  • CARD table with the fields:

    • id
    • creator_id
    • column_id
    • issue_id
    • note
    • archived
    • created_at
    • updated_at
    • is_deleted

  • ISSUE_PROJECT_HISTORY table with the fields:

    • issue_id
    • updated_at
    • actor_id
    • project_id
    • card_id
    • removed
    • column_name
    • previous_column_name

• Added is_deleted column to the MILESTONE table to capture deletes.

March 2019link

We have fixed a problem where the first commit in a git branch was skipped during our syncs. If any records in your COMMIT table were skipped prior to this change, you will need to initiate a re-sync to capture this data.

May 2018link

We have added a new field, archived, to the REPOSITORY table.

April 2018link

In the REQUESTED_REVIEWER_HISTORY table, the pull_request_id column now has a foreign key relationship to the PULL_REQUEST table.

In the ISSUE_MILESTONE_HISTORY table, the milestone_id field is now null for milestones that no longer exist.