Github
Setting up the Github connector
| No | Item | Required | Example | Notes |
|---|---|---|---|---|
| 1 | Authentication | Yes | Choose how to authenticate to GitHub Refer to the documentation in the form while using the connector OAuthPersonal Access Token | |
| 2 | Start date | Yes | 2021-03-01T00:00:00Z | The date from which you'd like to replicate data from GitHub in the format YYYY-MM-DDT00:00:00Z. For the streams which support this configuration, only data generated on or after the start date will be replicated. This field doesn't apply to all streams, see the docs for more info |
| 3 | GitHub Repositories | Yes | airbytehq/airbyte airbytehq/another-repo airbytehq/* airbytehq/airbyte | Space-delimited list of GitHub organizations/repositories, e.g. zipstackhq/zipstack for single repository, zipstackhq/* for get all repositories from organization and zipstackhq/zipstack zipstackhq/another-repo for multiple repositories. |
| 4 | Branch | No | airbytehq/airbyte/master airbytehq/airbyte/my-branch | Space-delimited list of GitHub repository branches to pull commits for, e.g. zipstackhq/zipstack/master. If no branches are specified for a repository, the default branch will be pulled. |
| 5 | Page size for large streams | No | The Github connector contains several streams with a large amount of data. The page size of such streams depends on the size of your repository. We recommended that you specify values between 10 and 30. |
Tables in the Github connector
| No | Table Name | Columns | Primary Keys | Read Mode | Inc. Sync Keys | API Info |
|---|---|---|---|---|---|---|
| 1 | commit_comment_reactions | 0 | id | Full Refresh, Incremental |
Table: commit_comment_reactions
| No | Column Name | Type | Notes || --- | ----------- | ---- | ----- |
External Resources
Zipstack Cloud features a powerful SQL querying engine on top of many types of connectors, including those from Trino, some custom connectors and connectors from the open source Airbyte project. Some Zipstack cloud connectors are designed to utilize and expand upon Airbyte's connector protocol, but they do not use Airbyte's EL core. Additionally, some parts of the documentation for these connectors have been adapted from the connector documentation found in Airbyte's open source project.