Connecting Nuon with your Version Control System (VCS) will give Nuon the ability to use your code when configuring your application. To use public repositories, you do not have to connect Nuon with your VCS. In this guide we’ll use the Nuon CLI to connect your Nuon Org to a GitHub account or repository and verify the connection is working by listing the connected repositories.Documentation Index
Fetch the complete documentation index at: https://docs.nuon.co/llms.txt
Use this file to discover all available pages before exploring further.
You may want to update an existing GitHub connection (e.g. add a new repository to the connection). To do this follow the steps below, make the updates with in the GitHub connection flow and your existing connection should be updated.
Select an Org
Because a VCS connection is scoped to your Nuon Org you’ll need to login using the CLI and select the Org you want to use.Start the connection flow
Now that you’re logged in with a valid Org selected you’ll want to kick off the GitHub connection flow with the CLI.Select GitHub access
At this point you’ll follow the GitHub connection flow, selecting an account to install Nuon Connect and selecting which repositories Nuon can have access to.

Verify connection works
At this point you can close the browser tab and verify everything is correct in the terminal via the CLI.Use Connected Repositories in Nuon
In a Component configuration file, you must use the[connected_repo] table syntax to reference a connected repository. For example:
components/my-component.toml
[public_repo] table syntax instead. If you use [public_repo] and the repository is private, Nuon will not be able to access it and will throw an error when you try to deploy the App.