Skip to main content
Theme

How-to

Connect the new instance to GitHub

The site's code lives on the new instance. Insites Console links each instance to one GitHub repository, and the link works both ways: a save in the CMS is committed to the repository, and a push to the repository is deployed to the instance. The tool does not send the code anywhere. It sends you to Console to make the link.

This is optional, and only shows where Insites has switched it on. When it is on, it replaces Send the code to GitHub. A dry run writes no code, so it has no GitHub step.

Where it is in the tool

  • In Verify, the step after Result is Connect GitHub.
  • The Report step of Launch has the same card.
  • The To do list has a job after cutover: Connect the instance to GitHub in Insites Console. Tick it once the link is made.

Connect it

  1. Press Open Insites Console. Console opens in a new tab, on your instances.
  2. Open the new instance. The step names its address, so you can find it.
  3. Open its GitHub section. Connect a repository you already have, or create a new one for the instance.
  4. Console shows the repository and branch once the instance is linked. From then on, each save in the CMS is committed there, and each push to it is deployed to the instance.

What the tool cannot see

  • Whether the instance is linked. The tool holds only the instance's access token, and Insites does not let that token read the GitHub link. Check in Console.
  • The GitHub section itself. Console opens an instance by its own id, which the tool does not have, so the button opens your instances list rather than the instance.

Each instance has one GitHub link. To link it to a different repository, change it in Console.