Skip to main content
GitHub Versioning lets you manage code for Notebooks and Queries through Git: link a Nekt resource to a GitHub repository, and every push to the configured branch (e.g. main) automatically triggers a redeploy in Nekt. You get version control, collaboration via pull requests, and a clear audit trail. This requires a workspace-wide GitHub connection: an owner or admin connects your organization in Settings → GitHub before you can link repositories to individual Notebooks or Queries. Once connected, you link a repo per resource (when creating or editing, or via the Versioning column in the list). After that, no manual “deploy” step is needed—Nekt stays in sync with your branch.

​
Prerequisite: Connect GitHub (workspace)

Before linking repositories, an owner or admin must connect your GitHub organization in Settings → GitHub. After that, you can link repos to individual Queries.

​
Prepare your repository

Use a GitHub repository to store your Query SQL. It can be empty. A dedicated repo per Query (or a shared repo with one file per query) keeps things clear. In the Queries list, use the Versioning column:
  1. Click Connect repository for the Query you want to version.
  2. In the dialog, select the GitHub repository (and branch, if offered) and confirm.
You can link or change the linked repo at any time from the same Versioning cell. If your workspace has no GitHub connection yet, the cell will prompt you to ask an admin to configure it in Settings.

​
Automatic deployments

Once a Query is linked, any push to the configured branch (typically main) automatically redeploys that Query in Nekt. The deployed SQL in Nekt stays in sync with the branch—no manual update needed.