GitHub (v1) | Stitch Documentation

GitHub is supported by the Singer community
This integration is powered by Singer's GitHub tap. For support, visit the GitHub repo or join the Singer Slack.

GitHub integration summary

Stitch’s GitHub integration replicates data using the GitHub REST API v3. Refer to the Schema section for a list of objects available for replication.

GitHub feature snapshot

A high-level look at Stitch's GitHub (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status	Deprecated on September 29, 2022	Supported by	Singer Community
Stitch plan	Standard	API availability	Not available
Singer GitHub repository	singer-io/tap-github
REPLICATION SETTINGS
Anchor Scheduling	Supported	Advanced Scheduling	Supported
Table-level reset	Unsupported	Configurable Replication Methods	Unsupported
DATA SELECTION
Table selection	Supported	Column selection	Supported
Select all	Supported
TRANSPARENCY
Extraction Logs	Supported	Loading Reports	Supported

Connecting GitHub

GitHub setup requirements

To set up GitHub in Stitch, you need:

Access to the projects you want to replicate data from. Stitch will only be able to access the same projects as the user who authorizes the connection in Stitch.

Step 1: Add GitHub as a Stitch data source

Sign into your Stitch account.
On the Stitch Dashboard page, click the Add Integration button.
Click the GitHub icon.
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

For example, the name “Stitch GitHub” would create a schema called stitch_github in the destination. Note: Schema names cannot be changed after you save the integration.
In the GitHub Repository Name field, enter the paths of the repositories you want to track. The path is relative to https://github.com. For example: The path for the Stitch Docs repository is stitchdata/docs

To track multiple repositories, enter a space delimited list of the repository paths. For example: stitchdata/docs stitchdata/docs-about-docs

Step 2: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your GitHub integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond GitHub’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 3: Create a replication schedule

Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the Replication Scheduling documentation for more information.

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

GitHub integrations support the following replication scheduling methods:

Replication Frequency
Anchor Scheduling
Advanced Scheduling using Cron (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 4: Authorize Stitch to access GitHub

Once you’ve configured the integration parameters, click Authorize. You will be prompted to grant Stitch access to your GitHub account.
Sign in to GitHub.
If you want to replicate data from private repositories, click Request next to the name of the relevant GitHub organization, then click Request approval from owners. The owners of the repository will then receive an email prompting them to approve or deny the request.

Note: This step is not needed if you only want to access public repositories. Any public repository, even within your work organization, should be available without approval from the owners.
Click Authorize singer-bot.

Once the authorization process is completed, you will be redirected to Stitch. You will be able to start replicating data from public repositories. The extraction from private repositories will fail until the owner has approved the access request.

Initial and historical replication jobs

After you finish setting up GitHub, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Initial replication jobs with Anchor Scheduling

If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Replication will continue after the seven days are over. If you’re no longer interested in this source, be sure to pause or delete the integration to prevent unwanted usage.

GitHub table reference

Schemas and versioning

Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.

The schema and info displayed below is for version 1 of this integration.

Table and column names in your destination

Depending on your destination, table and column names may not appear as they are outlined below.

For example: Object names are lowercased in Redshift (CusTomERs > customers), while case is maintained in PostgreSQL destinations (CusTomERs > CusTomERs). Refer to the Loading Guide for your destination for more info.

assignees

The assignees table contains info about the available assignees for issues in the repositories specified for the integration.

Replication Method

Full Table

Primary Key

Useful links

GitHub documentation

assignees schema on GitHub

GitHub API method

assignees table schema

_sdc_repository

STRING

INTEGER

login

STRING

type

STRING

url

STRING

collaborators

The collaborators table contains info about the users who contribute to the repositories specified for the integration.

For organization-owned repositories, this will include outside collaborators, organization owners, organization members that are direct collaborators, who have access through team memberships, or have access through default organization permissions.

Replication Method

Full Table

Primary Key

Useful links

collaborators schema on GitHub

GitHub API method

collaborators table foreign keys

Join collaborators with	on
pull_requests	collaborators.id = pull_requests.user.id
reviews	collaborators.id = reviews.user.id

collaborators table schema

_sdc_repository

STRING

INTEGER

login

STRING

type

STRING

url

STRING

comments

The comments table contains info about comments made on issues in the repositories specified for the integration.

Replication Method

Key-based Incremental

Primary Key

Useful links

GitHub documentation

comments schema on GitHub

GitHub API method

comments table schema

_sdc_repository

STRING

author_association

STRING

body

STRING

created_at

DATE-TIME

home_url

STRING

html_url

STRING

INTEGER

issue_url

STRING

node_id

STRING

updated_at

DATE-TIME

url

STRING

user

OBJECT

Click to expand user

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

STRING

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

commit_comments

The commit_comments table contains info about the commit comments in the repositories specified for the integration.

Replication Method	Key-based Incremental
Primary Key	id
Replication Key	updated_at
Useful links	commit_comments schema on GitHub GitHub API method

commit_comments table schema

body

STRING

commit_id

STRING

created_at

DATE-TIME

html_url

STRING

NUMBER

line

NUMBER

node_id

STRING

path

STRING

position

NUMBER

updated_at

DATE-TIME

url

STRING

user

OBJECT

Click to expand user

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

NUMBER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

commits

The commits table contains info about repository commits in a project.

Replication Method

Key-based Incremental

Primary Key

sha

Useful links

GitHub documentation

commits schema on GitHub

GitHub API method

commits table foreign keys

Join commits with	on
events	commits.sha = events.payload.commits.sha
pr_commits	commits.sha = pr_commits.sha

commits table schema

_sdc_repository

STRING

comments_url

STRING

commit

OBJECT

Click to expand commit

author

OBJECT

Click to expand author

date

DATE-TIME

email

STRING

login

STRING

name

STRING

comment_count

INTEGER

committer

OBJECT

Click to expand committer

date

DATE-TIME

email

STRING

login

STRING

name

STRING

message

STRING

tree

OBJECT

Click to expand tree

sha

STRING

url

STRING

url

STRING

files

ARRAY

Click to expand files

additions

NUMBER

blob_url

STRING

changes

NUMBER

deletions

NUMBER

filename

STRING

patch

STRING

raw_url

STRING

status

STRING

html_url

STRING

parents

ARRAY

Click to expand parents

html_url

STRING

sha

STRING

url

STRING

sha

STRING

url

STRING

events

The events table contains information about events in the repositories specified for the integration.

Replication Method

Key-based Incremental

Primary Key

Useful links

GitHub documentation

events schema on GitHub

GitHub API method

events table foreign keys

Join events with	on
commits	events.payload.commits.sha = commits.sha
pr_commits	events.payload.commits.sha = pr_commits.sha

events table schema

_sdc_repository

STRING

actor

OBJECT

Click to expand actor

avatar_url

STRING

display_login

STRING

gravatar_id

STRING

NUMBER

login

STRING

url

STRING

created_at

STRING

distinct_size

NUMBER

head

STRING

NUMBER

org

OBJECT

Click to expand org

avatar_url

STRING

gravatar_id

STRING

NUMBER

login

STRING

url

STRING

payload

OBJECT

Click to expand payload

action

STRING

before

STRING

comment

STRING

commits

ARRAY

Click to expand commits

author

OBJECT

Click to expand author

email

STRING

name

STRING

distinct

BOOLEAN

message

STRING

sha

STRING

url

STRING

description

STRING

issue

STRING

master_branch

STRING

pusher_type

STRING

ref

STRING

ref_type

STRING

public

BOOLEAN

push_id

NUMBER

ref

STRING

repo

OBJECT

Click to expand repo

NUMBER

name

STRING

url

STRING

size

NUMBER

type

STRING

issue_events

The issue_events table contains info about issue events in the repositories specified for the integration.

Replication Method

Key-based Incremental

Primary Key

Useful links

issue_events schema on GitHub

GitHub API method

issue_events table foreign keys

Join issue_events with	on
reviews	issue_events.commit_id = reviews.commit_id
review_comments	issue_events.commit_id = review_comments.commit_id issue_events.commit_id = review_comments.original_commit_id
issues	issue_events.id = issues.id
pull_requests	issue_events.id = pull_requests.id

issue_events table schema

_sdc_repository

STRING

actor

OBJECT

Click to expand actor

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

assignee

OBJECT

Click to expand assignee

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

assigner

OBJECT

Click to expand assigner

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

commit_id

STRING

commit_url

STRING

created_at

DATE-TIME

event

STRING

INTEGER

issue

OBJECT

Click to expand issue

active_lock_reason

STRING

assignee

OBJECT

Click to expand assignee

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

assignees

ARRAY

Click to expand assignees

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

author_association

STRING

body

STRING

closed_at

DATE-TIME

comments

INTEGER

comments_url

STRING

created_at

DATE-TIME

events_url

STRING

html_url

STRING

INTEGER

labels

ARRAY

Click to expand labels

color

STRING

default

BOOLEAN

description

STRING

INTEGER

name

STRING

node_id

STRING

url

STRING

labels_url

STRING

locked

BOOLEAN

milestone

OBJECT

Click to expand milestone

closed_at

STRING

closed_issues

INTEGER

created_at

DATE-TIME

creator

OBJECT

Click to expand creator

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

description

STRING

due_on

DATE-TIME

html_url

STRING

INTEGER

labels_url

STRING

node_id

STRING

number

INTEGER

open_issues

INTEGER

state

STRING

title

STRING

updated_at

DATE-TIME

url

STRING

node_id

STRING

number

INTEGER

performed_via_github_app

STRING

pull_request

OBJECT

Click to expand pull_request

diff_url

STRING

html_url

STRING

patch_url

STRING

url

STRING

repository_url

STRING

state

STRING

title

STRING

updated_at

DATE-TIME

url

STRING

user

OBJECT

Click to expand user

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

label

OBJECT

Click to expand label

color

STRING

name

STRING

node_id

STRING

performed_via_github_app

STRING

rename

OBJECT

Click to expand rename

from

STRING

requested_reviewer

OBJECT

Click to expand requested_reviewer

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

review_requester

OBJECT

Click to expand review_requester

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

url

STRING

issue_labels

The issue_labels table contains info about issue labels in the repositories specified for the integration.

Replication Method

Key-based Incremental

Primary Key

Useful links

issue_labels schema on GitHub

GitHub API method

issue_labels table foreign keys

Join issue_labels with	on
issues	issue_labels.id = issues.labels.id
pull_requests	issue_labels.id = pull_requests.labels.id

issue_labels table schema

_sdc_repository

STRING

color

STRING

default

BOOLEAN

description

STRING

NUMBER

name

STRING

node_id

STRING

url

STRING

issue_milestones

The issue_milestones table contains info about issue milestones in the repositories specified for the integration.

Replication Method

Key-based Incremental

Primary Key

Useful links

issue_milestones schema on GitHub

GitHub API method

issue_milestones table schema

_sdc_repository

STRING

closed_at

DATE-TIME

closed_issues

NUMBER

created_at

DATE-TIME

creator

OBJECT

Click to expand creator

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

NUMBER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

description

STRING

due_on

DATE-TIME

html_url

STRING

NUMBER

labels_url

STRING

node_id

STRING

number

NUMBER

open_issues

NUMBER

state

STRING

title

STRING

updated_at

DATE-TIME

url

STRING

issues

The issues table contains info about issues in the repositories specified for the integration.

Issues and pull requests

GitHub’s API considers every pull request an issue, but not every issue may be a pull request. Therefore, this table may contain both issues and pull requests.

Replication Method

Key-based Incremental

Primary Key

Useful links

GitHub documentation

issues schema on GitHub

GitHub API method

issues table foreign keys

Join issues with	on
issue_events	issues.id = issue_events.id
pull_requests	issues.id = pull_requests.id issues.labels.id = pull_requests.labels.id
issue_labels	issues.labels.id = issue_labels.id
pr_commits	issues.id = pr_commits.pr_id

issues table schema

_sdc_repository

STRING

assignee

OBJECT

author_association

STRING

body

STRING

closed_at

DATE-TIME

comments

INTEGER

comments_url

STRING

created_at

DATE-TIME

events_url

STRING

html_url

STRING

INTEGER

labels

ARRAY

Click to expand labels

color

STRING

default

BOOLEAN

description

STRING

INTEGER

name

STRING

node_id

STRING

url

STRING

labels_url

STRING

locked

BOOLEAN

node_id

STRING

number

INTEGER

pull_request

OBJECT

Click to expand pull_request

diff_url

STRING

html_url

STRING

patch_url

STRING

url

STRING

repository_url

STRING

state

STRING

title

STRING

updated_at

DATE-TIME

url

STRING

user

OBJECT

Click to expand user

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

INTEGER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

type

STRING

url

STRING

project_cards

The project_cards table contains information about project cards in the repositories specified for the integration.

Note: In order to replicate this table, you must also set the project table to replicate.

Replication Method	Key-based Incremental
Primary Key	id
	project
Useful links	GitHub documentation project_cards schema on GitHub GitHub API method

project_cards table schema

_sdc_repository

STRING

archived

BOOLEAN

cards_url

STRING

column_url

STRING

content_url

STRING

created_at

DATE-TIME

creator

OBJECT

Click to expand creator

NUMBER

login

STRING

NUMBER

name

STRING

node_id

STRING

note

STRING

project_url

STRING

updated_at

DATE-TIME

url

STRING

project_columns

The project_columns table contains info about the columns of projects in the repositories specified for the integration.

Note: In order to replicate this table, you must also set the project table to replicate.

Replication Method	Key-based Incremental
Primary Key	id
	project
Useful links	project_columns schema on GitHub GitHub API method

project_columns table schema

_sdc_repository

STRING

cards_url

STRING

created_at

DATE-TIME

NUMBER

name

STRING

node_id

STRING

project_url

STRING

updated_at

DATE-TIME

url

STRING

projects

The projects table contains info about projects in the repositories specified for the integration.

Replication Method

Key-based Incremental

Primary Key

Useful links

projects schema on GitHub

GitHub API method

projects table schema

body

STRING

columns_url

STRING

created_at

DATE-TIME

creator

OBJECT

Click to expand creator

NUMBER

login

STRING

html_url

STRING

NUMBER

name

STRING

node_id

STRING

number

NUMBER

owner_url

STRING

state

STRING

updated_at

DATE-TIME

url

STRING

pull_requests

The pull_requests table contains info about pull requests made against the repositories specified for the integration.

Replication Method

Key-based Incremental

Primary Key

Useful links

GitHub documentation

pull_requests schema on GitHub

GitHub API method

pull_requests table foreign keys

Join pull_requests with	on
collaborators	pull_requests.user.id = collaborators.id
reviews	pull_requests.user.id = reviews.user.id
issues	pull_requests.id = issues.id pull_requests.labels.id = issues.labels.id
issue_events	pull_requests.id = issue_events.id
issue_labels	pull_requests.labels.id = issue_labels.id
pr_commits	pull_requests.id = pr_commits.pr_id

pull_requests table schema

_sdc_repository

STRING

base

OBJECT

Click to expand base

label

STRING

ref

STRING

repo

OBJECT

Click to expand repo

INTEGER

name

STRING

url

STRING

sha

STRING

body

STRING

closed_at

DATE-TIME

created_at

DATE-TIME

STRING

labels

ARRAY

Click to expand labels

color

STRING

default

BOOLEAN

description

STRING

INTEGER

name

STRING

node_id

STRING

url

STRING

merged_at

DATE-TIME

number

INTEGER

state

STRING

title

STRING

updated_at

DATE-TIME

url

STRING

user

OBJECT

Click to expand user

INTEGER

login

STRING

releases

The releases table contains info about releases in the repositories specified for the integration.

Note: GitHub doesn’t include regular Git tags that haven’t been associated with a release.

Replication Method

Full Table

Primary Key

Useful links

releases schema on GitHub

GitHub API method

releases table schema

_sdc_repository

STRING

author

OBJECT

Click to expand author

INTEGER

login

STRING

body

STRING

created_at

DATE-TIME

draft

BOOLEAN

html_url

STRING

name

STRING

prerelease

BOOLEAN

published_at

DATE-TIME

tag_name

STRING

target_commitish

STRING

url

STRING

review_comments

The review_comments table contains info about comments made on pull request reviews in the repositories specified for the integration.

Note: In order to replicate this table, you must also set the pull_request table to replicate.

Replication Method	Key-based Incremental
Primary Key	id
	pull_request
Useful links	review_comments schema on GitHub GitHub API method

review_comments table foreign keys

Join review_comments with

issue_events

review_comments.commit_id = issue_events.commit_id

review_comments.original_commit_id = issue_events.commit_id

reviews

review_comments.commit_id = reviews.commit_id

review_comments.original_commit_id = reviews.commit_id

review_comments.pull_request_review_id = reviews.id

review_comments table schema

_sdc_repository

STRING

assignee

STRING

assignees

STRING

author_association

STRING

base

STRING

body

STRING

comments_url

STRING

commit_id

STRING

commits_url

STRING

created_at

DATE-TIME

diff_hunk

STRING

diff_url

STRING

head

STRING

html_url

STRING

INTEGER

in_reply_to_id

INTEGER

issue_url

STRING

labels

STRING

locked

STRING

merge_commit_sha

STRING

milestone

STRING

node_id

STRING

original_commit_id

STRING

original_position

INTEGER

patch_url

STRING

path

STRING

position

INTEGER

pull_request_review_id

INTEGER

pull_request_url

STRING

requested_reviewers

STRING

requested_teams

STRING

review_comment_url

STRING

review_comments_url

STRING

statuses_url

STRING

updated_at

DATE-TIME

user

OBJECT

Click to expand user

INTEGER

login

STRING

reviews

The reviews table contains info about pull request reviews in the repositories specified for the integration. A pull request review is a group of comments on a pull request.

Note: In order to replicate this table, you must also set the pull_request table to replicate.

Replication Method	Key-based Incremental
Primary Key	id
	pull_request
Useful links	GitHub documentation reviews schema on GitHub GitHub API method

reviews table foreign keys

Join reviews with	on
collaborators	reviews.user.id = collaborators.id
pull_requests	reviews.user.id = pull_requests.user.id
issue_events	reviews.commit_id = issue_events.commit_id
review_comments	reviews.commit_id = review_comments.commit_id reviews.commit_id = review_comments.original_commit_id reviews.id = review_comments.pull_request_review_id

reviews table schema

_sdc_repository

STRING

body

STRING

commit_id

STRING

html_url

STRING

INTEGER

pull_request_url

STRING

state

STRING

submitted_at

DATE-TIME

user

OBJECT

Click to expand user

INTEGER

login

STRING

stargazers

The stargazers table contains info about users who have starred the repositories specified for the integration.

Replication Method

Key-based Incremental

Primary Key

user_id

Useful links

stargazers schema on GitHub

GitHub API method

stargazers table schema

_sdc_repository

STRING

starred_at

DATE-TIME

user

OBJECT

Click to expand user

INTEGER

user_id

INTEGER

team_members

The team_members table contains info about members of organization teams that are visible to the user who authorized the integration.

Note: In order to replicate this table, you must also set the team table to replicate.

Replication Method	Key-based Incremental
Primary Key	id
	team
Useful links	team_members schema on GitHub GitHub API method

team_members table schema

_sdc_repository

STRING

avatar_url

STRING

events_url

STRING

followers_url

STRING

following_url

STRING

gists_url

STRING

gravatar_id

STRING

html_url

STRING

NUMBER

login

STRING

node_id

STRING

organizations_url

STRING

received_events_url

STRING

repos_url

STRING

site_admin

BOOLEAN

starred_url

STRING

subscriptions_url

STRING

team_slug

STRING

type

STRING

url

STRING

team_memberships

The team_memberships table contains info about membership of users in of organization teams that are visible to the user who authorized the integration.

Note: In order to replicate this table, you must also set the team table to replicate.

Replication Method	Key-based Incremental
Primary Key	url
	team
Useful links	team_memberships schema on GitHub GitHub API method

team_memberships table schema

_sdc_repository

STRING

role

STRING

state

STRING

url

STRING

teams

The teams table contains info about the teams in an organization. Only teams that are visible to the user who authorized the integration in Stitch will be replicated.

Replication Method

Key-based Incremental

Primary Key

Useful links

teams schema on GitHub

GitHub API method

teams table schema

_sdc_repository

STRING

description

STRING

html_url

STRING

NUMBER

members_url

STRING

name

STRING

node_id

STRING

parent

OBJECT, STRING

permission

STRING

privacy

STRING

repositories_url

STRING

slug

STRING

url

STRING

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.

Related	Troubleshooting
Destination & Integration Compatibility Replication Scheduling Syncing Historical SaaS Data Resetting Replication Keys Nested Data Structures & Row Count Impact	Third-Party Downtime Understanding & Reducing Your Usage Re-Authorizing Integrations Replication Issues