> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub

> Workspace-wide GitHub connection for version control and deploy-from-commit.

The **GitHub** integration is a workspace-wide connection to your GitHub organization. Once connected, you can use **GitHub Versioning** for [Notebooks](/notebooks/versioning) and [Queries](/queries/versioning): link each resource to a repository, keep code in Git, and have Nekt automatically redeploy when you push to the configured branch.

<Info>
  GitHub Versioning is **only available on Growth or Custom plans**.
</Info>

## Connect your GitHub organization

Before linking repositories to individual Notebooks or Queries, an owner or admin must connect the workspace to GitHub.

1. Go to **Settings → GitHub** in Nekt.
2. Click **Connect to GitHub**.
3. Approve the Nekt GitHub App for your GitHub organization when redirected.

After installation, the page shows your connected organization. You can **Remove** the connection at any time; doing so does not delete your GitHub repos, but Nekt will no longer sync or deploy from them.

## What you can do after connecting

* **Notebooks:** Link a Notebook to a GitHub repo (when creating or editing the Notebook, or via the Versioning column in the Notebooks list). Pushes to the linked branch (e.g. `main`) trigger an automatic redeploy of the Notebook in Nekt.
* **Queries:** Link a Query to a GitHub repo via the Versioning column in the Queries list. Pushes to the linked branch trigger an automatic redeploy of the Query in Nekt.

Code lives in your repository; Nekt stays in sync with the branch you chose. For step-by-step usage in each module, see [Versioning (Notebooks)](/notebooks/versioning) and [Versioning (Queries)](/queries/versioning).