Skip to content

Instance · Integrations

Git Repository Introduction

Last updated 1 November 2026

Keep a history of your code and deploy from Git: the Insites GitHub App and the Git Repository screen.

Version control keeps a history of every change to your site's code, so you can see who changed what and undo a change. Insites connects your instance to a Git repository in two ways. One is the Insites GitHub App, set up through CloudShell. The other is the Git Repository screen in Integrations.

The Insites GitHub App

Connect one GitHub repository to your instance. Every push to the branch the instance watches is deployed automatically, with the instance's own credentials. If a GitHub deploy fails, it is tried again after 60 seconds. When the connection is made, the watched branch is protected on GitHub, so nobody can force-push to it or delete it.

You set it up by asking your AI assistant, with CloudShell connected and your instance selected:

Connect GitHub to my instance.

CloudShell replies with a one-time install link. Install the app on the one repository for this instance. CloudShell also has tools to check the connection, list GitHub deploys, change the watched branch and revert a commit.

The Git Repository screen

In the admin, open Integrations and choose Git Repository. It holds the repository credentials, a Sync CMS changes to Git switch, and the SSH configuration, and has an Event Stream tab.

Note

The GitHub App facts come from the Logic Engine deployment reference and the CloudShell tools. The Git Repository screen comes from the CRM module source. Neither was changed for this page.

Common mistakes

  • Giving the GitHub App access to all repositories. It may pick the wrong one; choose only the one repository.
  • Editing in the admin and pushing to the watched branch. The next deploy from Git replaces the admin edit.
  • Pushing work in progress to the watched branch. Use another branch and merge when it is ready.