Skip to main content Skip to complementary content

GitHub 

GitHub is a platform and cloud-based service for software development and version control using Git. You can use GitHub as a data source when landing or replicating data.

For more information on the API, see GitHub REST API documentation.

Supported update methods

For more information, see An overview of target update methods.

  • Change data capture (CDC)

  • Reload and compare

  • Change data capture (CDC) using Change Tables

  • Full load

  • Change data capture (CDC)

  • Reload

Preparing for authentication

To access your GitHub data, you need to authenticate the connection with your account credentials.

Create a GitHub personal access token and grant the following scopes:

  • repo

  • read:org

  • read:user

  • read:project.

For more information, see Managing your personal access tokens

Information noteMake sure that the account you use has read access to the tables you want to fetch.

Creating the connection

For more information, see Connecting to SaaS applications.

  1. Fill in the required connection properties.
  2. Provide a name for the connection in Connection name.

  3. Select Open connection metadata to define metadata for the connection when it has been created.

  4. Click Create.

Connection settings
Setting Description
Data gateway

Select a Data Movement gateway if required by your use case.

Information note

This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None.

For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.

Organization

The name of your organization in GitHub.

Personal access token

The personal access token that you generated when preparing for authentication.

For more information, see Preparing for authentication.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!