Release Notes

August 2020

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 2020

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 2019

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 2019

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 2019

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 2018

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

April 2018

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.

Documentation