{"id":2210,"date":"2024-11-22T11:59:39","date_gmt":"2024-11-22T11:59:39","guid":{"rendered":"https:\/\/community.cyclr.com\/?post_type=docs&p=2210"},"modified":"2026-04-22T10:48:32","modified_gmt":"2026-04-22T10:48:32","password":"","slug":"github-integration","status":"publish","type":"docs","link":"https:\/\/community.cyclr.com\/user-documentation\/cyclr-console\/github-integration","title":{"rendered":"GitHub Integration"},"content":{"rendered":"\n

<\/span><\/a>Overview<\/span><\/h2>\n\n\n\n

Cyclr\u2019s GitHub Integration<\/strong> feature enables you to export Template Releases directly to your own GitHub repository. You can also import Template Releases from your GitHub repository.<\/p>\n\n\n\n

This provides you with a way to transfer Template Releases between Consoles if you have more than one Console, as well as an additional way to store backups of your Templates.<\/p>\n\n\n\n

When you export a Template Release<\/a> through the separate Export Release button, the resulting JSON file you would download contains all the information to re-create that Template Release, including the Releases of any Connectors used by it. That same mechanism is used by the GitHub Integration feature, but instead of downloading the file, it\u2019s sent straight to your GitHub repository.<\/p>\n\n\n\n

You\u2019re also able to import Templates previously exported to GitHub into another Cyclr Console that\u2019s configured to work with the same repository, which is how you can transfer them.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\" Note: GitHub Integration and permissions<\/strong>
To configure the GitHub Integration\u00a0feature, your Console User will need to have the Cyclr GitHub Integration \u201cEdit\u201d\u00a0Permission<\/a>\u00a0enabled.
Once setup with valid details, any Console User with appropriate Permissions to Export or Import Template Releases will be able to send them to\/retrieve them from GitHub.<\/p>\n\n\n\n

<\/div>\n\n\n\n

<\/span><\/a>Configuration<\/span><\/h2>\n\n\n\n

Before the feature can be used, you must provide your Cyclr Console with the details to connect to your GitHub repository. You\u2019ll also need to generate a \u201cpersonal access token\u201d from within GitHub.<\/p>\n\n\n\n

Go to a Cyclr Console, then Settings > GitHub Integration:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

You can decide to use the same details here for multiple Cyclr Consoles so they all point to the same repository and branch, and only change the Environment Name for each so they have their own folders there.<\/p>\n\n\n\n

Explanation of those details:<\/p>\n\n\n\n

Field<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
GitHub Repository Owner<\/td>Owner of the GitHub repository to connect to.<\/td><\/tr>
GitHub Repository Name<\/td>Name of the GitHub repository to connect to.<\/td><\/tr>
GitHub Branch Name<\/td>Name of a branch within the GitHub repository to work in.<\/td><\/tr>
GitHub personal access token<\/td>Used to obtain access to the repository.

This should have \u201cRead and write\u201d permission on the repository.<\/td><\/tr>
Environment Name<\/td>Used by this Cyclr Console as the name of a folder to work in using the above details.

Note: If you have multiple Cyclr Consoles for different stages of your development process, you could use this field to provide values such as \u201cdevelopment\u201d and \u201cproduction\u201d to enable each Console to store copies of Template Releases separately. You can then import other Consoles’ Template Releases.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

When selecting the Save<\/strong> button, Cyclr will immediately attempt to connect to the GitHub repository using the details provided. If that is unsuccessful for any reason – such as invalid details or the access token having expired – Cyclr won\u2019t save those changes.<\/p>\n\n\n\n

If it\u2019s successful, a folder will be created in the repository using the value provided in the Console\u2019s Environment Name, and that will contain a basic README.md<\/code> file.<\/p>\n\n\n\n

<\/div>\n\n\n\n

<\/span><\/a>Push Template Release to GitHub<\/span><\/h2>\n\n\n\n

If Cyclr has valid GitHub details – and your Console User has the Templates \u201cView\u201c Permission<\/a> – when you view the Releases of any Template in your Cyclr Console, there will be an additional Push Release to GitHub<\/strong> button shown:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Selecting that button will immediately push the Template Release to your GitHub repository.<\/p>\n\n\n\n

The first time you push a Template Release, Cyclr will create a new folder called \u201cTemplates\u201d in GitHub and your Template Release will be created there as a JSON file.<\/p>\n\n\n\n

<\/div>\n\n\n\n

<\/span><\/a>Import Template Release from GitHub<\/span><\/h2>\n\n\n\n

Having exported a Template Release to your GitHub repository from one Console, you can then import it from GitHub into another Console, provided your Console User has the Templates \u201cEdit\u201d Permission<\/a>.<\/p>\n\n\n\n

When importing Template Releases from GitHub, you can choose to:<\/p>\n\n\n\n