Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Pushing an API version to GitHub

Link your API to a GitHub repository and push your API definition in OAS/Swagger or RAML.

Before you begin

  • You have a GitHub account and a repository.
  • Your browser is supported by GitHub (since Internet Explorer 11 is no longer supported by GitHub, this feature is not supported by Talend Cloud API Designer for IE11).

Procedure

  1. If your GitHub account is not linked to your Talend Cloud API Designer account yet, go to the API Designer settings.
  2. Click Link your GitHub account.
    GitHub account section in API Designer settings.
  3. In the window that opens, sign in to GitHub and click Authorize Talend to allow Talend Cloud API Designer to access your GitHub account.
    Information noteWarning: If you are using Internet Explorer 11, you will be prompted to upgrade to the latest version of Microsoft Edge, Google Chrome or Firefox.

    Your GitHub account is now linked to your Talend Cloud API Designer account and you can start pushing your API definitions to GitHub.

  4. Open the API version that you want to push to GitHub.
  5. Click Link at the top-right corner.
  6. In the Edit GitHub settings section, enable the option and edit the following fields:
    • Owner
    • Repository
    • Branch
    • Path
    • Format
    In the Format drop-down list, you can choose to export your definition with Talend extensions or in an API Gateway compatibility mode.
    Information noteNote: If your API has several versions, each version can have different GitHub settings.
    Edit GitHub settings section of the API Settings view.
  7. Once your settings are saved, click Push.
    A green dot appears to the right of Push when your project contains changes that have not been pushed to GitHub.
    Screenshot of the project when it contains changes that have not been pushed to GitHub.
  8. Enter a commit message and a tag if needed, then click Push.
    A tag should be unique and should follow these rules:
    • It can contain only alphanumeric characters and the following special characters: _, -, . and /.
    • It cannot start or end with a special character.
    • It cannot contain the following character patterns: .., // and /..

Results

The selected version of your API definition is pushed to your repository. The name of the file generated contains the name of the API and the version.

You can click View on GitHub to open the selected repository.

In this section

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 – please let us know!

Leave your feedback here