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).
- Open the API version that you want to push to GitHub and click Settings.
If your GitHub account is not linked to your Talend Cloud API Designer account yet, click
Link your GitHub account.
In the window that opens, sign in to GitHub and click
Authorize Talend to allow Talend Cloud API Designer to access your GitHub
Warning: 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 you API definitions to GitHub.
In your API settings, use the drop-down lists to select the
Owner, the Repository, the Branch
and the Format, then enter a Path and click Save.
In the Format drop-down list, you can choose to export your definition with Talend extensions or in an API Gateway compatibility mode.Note: If your API has several versions, each version can have different GitHub settings.
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.
Enter a commit message and a tag if needed, then click
A tag should be unique and should follow these rules:
- It can contain only alphanumeric characters and the
following special characters:
- It cannot start or end with a special character.
- It cannot contain the following character patterns:
- It can contain only alphanumeric characters and the following special characters:
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.