Release Notes

September 2024

We have added support for GitHub App authentication.

July 2024

The GitHub connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

September 2023

We have added the repository_id column as a primary key in the SECURITY_ALERT table.

We have added a new column, payload, to the DEPLOYMENT table.

August 2023

We have added the following new columns to the PULL_REQUEST table:

• active_lock_reason
• closed_at
• created_at
• updated_at

We have added the ability to include several personal access tokens in the setup form in order to avoid exceeding GitHub's request rate limit. This feature is available to all connectors set up after August 26, 2023. Learn more in our setup guide.

July 2023

We now incrementally sync the WORKFLOW_RUN table daily to capture new records.

We have added the following new tables:

• SECURITY_ADVISORY
• SECURITY_ADVISORY_CWE
• SECURITY_ADVISORY_VULNERABILITY
• SECURITY_ALERT
• SECURITY_CWE
• SECURITY_REFERENCE
• SECURITY_VULNERABILITY

We are gradually rolling out this change to all existing connectors.

The repository_id column in the WORKFLOW and WORKFLOW_RUN tables now has a foreign key relationship to the REPOSITORY table.

April 2023

We have added the following new tables:

• WORKFLOW
• WORKFLOW_RUN
• WORKFLOW_RUN_PULL_REQUEST

We are gradually rolling out these changes to all existing connectors.

March 2023

We have added two new columns, forks_count and watchers_count, to the REPOSITORY table.

August 2022

We have added a new table, BRANCH_COMMIT_RELATION, that stores information about branch and commit mapping.

We are gradually rolling out this feature to all existing connectors. Once this feature is available, you will see the BRANCH_COMMIT_RELATION table on the Schema tab. To fetch data for all existing branches and commits, re-sync your connector.

We have added a new table, REPOSITORY_TOPIC, that stores information about repository topics.

We are gradually rolling out this feature to all existing connectors. Once this feature is available, you will see the REPOSITORY_TOPIC table on the Schema tab.

June 2022

We have added a new column, pull_request_review_id to the PULL_REQUEST_REVIEW_COMMENTS table. This column links to the PULL_REQUEST_REVIEW table.

We now sync all users from any team associated with a repository. Previously, we may have missed syncing some users.

April 2022

We have added a new table, PULL_REQUEST_READY_FOR_REVIEW_HISTORY, that stores the history of the convert_to_draft and ready_for_review events.

We are gradually rolling out this feature to all existing connectors. Once this feature is available, you will see the PULL_REQUEST_READY_FOR_REVIEW_HISTORY table on the Schema tab. To fetch events for all pull requests, re-sync your connector.

NOTE: The readyForReview column defines events in two ways:

• false - marks an event as convert_to_draft.
• true - marks an event as ready_for_review.

March 2022

We now sync data for review comments on a pull request to the PULL_REQUEST_REVIEW_COMMENT table. We are gradually rolling out this feature to all existing connectors. Once this feature is available, you will see the PULL_REQUEST_REVIEW_COMMENT table on the Schema tab. To fetch comments for all pull requests, re-sync your connector.

February 2022

We have added a new table, STARGAZER, that stores information about repository stargazers.

We no longer update the stargazers_count column of the REPOSITORY table. For connectors created after February 9, 2022, this column is not present in the REPOSITORY table.

January 2022

We have added a new column, stargazers_count, to the REPOSITORY table.

We have changed the schema of the REQUESTED_REVIEW_HISTORY table. We added the requested_reviewer_type column and changed the requested_id column.

We now sync the requested_reviewer and requested_team as separate requested reviewer types. In the new schema, the requested_id column's value is the ID from either requested_reviewer or requested_team. The requested_reviewer_type column has either user or team as a value, depending on the requested reviewer type. Previously, we synced only requested_reviewer.

This feature is available for connectors created after February 1, 2022. If you want to enable the feature for connectors created before February 2, 2022, contact our support team.

December 2021

You can now opt to use a Personal access token to authenticate GitHub. For more information, see our setup instructions.

October 2021

We have added the following new tables:

• COMMIT_PULL_REQUEST stores linking information between commits and their relevant pull requests

  NOTE: Re-sync your connector to sync the data for all commits.

• DEPLOYMENT stores deployment information

• DEPLOYMENT_STATUS stores deployment status information

• 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 can manage the tables from the Schema tab of your Fivetran dashboard.

April 2021

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 2021

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

December 2020

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

August 2020

We have released pre-built, dbt Core-compatible data models for GitHub. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

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 following columns:

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

• COLUMN table with the following columns:

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

• CARD table with the following columns:

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

• ISSUE_PROJECT_HISTORY table with the following columns:

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

We have added the 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.