GitHub
Studio can take a project that exists only on your machine and put it on GitHub — account sign-in, repository creation, and the first push — without leaving the app. Once it's there, every Commit and sync from the Source Control panel keeps the repository current, and your host can build the site from it.
Authorize Studio
The first time you use a GitHub feature, Studio asks you to sign in with a one-time code:
A Sign in to GitHub dialog appears showing a short code.
Click the link in the dialog — it opens GitHub's device-authorization page in your browser.
Enter the code there and approve the request.
Back in Studio, the dialog closes on its own once GitHub confirms.
Studio remembers the authorization on this device, so you won't be asked again on your next publish.
Publish to GitHub
Publish to GitHub lives in the Source Control panel — it's offered when your project isn't a repository yet, and again in the sync bar while the project has no remote.
Click Publish to GitHub . Sign in first if prompted.
In the dialog, confirm the Repository name (prefilled with your project's name) and add an optional Description .
Choose the visibility. Private repository is on by default — turn it off to make the code public.
Click Create Repository .
Studio creates the repository on GitHub, connects your project to it, and pushes everything up. The status bar reports each step, and when it finishes, the Source Control panel switches from Local only (no remote) to live sync status — you're one Commit and sync away from publishing changes from now on.
Publishing uploads your project's files to GitHub. With Private repository on, only you (and people you invite on GitHub) can see them; public repositories are visible to anyone.
Some Studio platforms connect to GitHub through the Jx Suite GitHub App instead — when that applies, the Welcome screen offers Install the Jx Suite GitHub App and an Add Existing Repository… picker for repositories your account can already reach. The picker's footer links to the App's repository-access settings for each account, so you can widen what Studio sees at any time — see Repository access .
Next
Source control — the day-to-day commit and sync flow
Publish — how a push becomes a live site