Remove variable api page

docs/source-control-environments/create-environments.md

@@ -118,4 +118,3 @@ Learn more about:
 
 * [Environments in n8n](/source-control-environments/understand/environments.md) and [Git and n8n](/source-control-environments/understand/git.md)
 * [Source control patterns](/source-control-environments/understand/patterns.md)
-* Reusable [Variables](/code/variables.md) and [Managing variables using the API](/source-control-environments/using/manage-variables.md) when using source control.

docs/source-control-environments/index.md

@@ -23,7 +23,6 @@ In this section:
 * [Using](/source-control-environments/using/index.md):
 	* [Push and pull](/source-control-environments/using/push-pull.md): Send work to Git, and fetch work from Git to your instance.
 	* [Copy work between environments](/source-control-environments/using/copy-work.md): How to copy work between different n8n instances.
-	* [Manage variables](/source-control-environments/using/manage-variables.md): Manage variable values using the n8n API and source control.
 * [Tutorial: Create environments with source control](/source-control-environments/create-environments.md): An end-to-end tutorial, setting up environments using n8n's recommended configurations.
 
 Related sections:

docs/source-control-environments/understand/environments.md

@@ -32,7 +32,7 @@ In n8n, an environment comprises two parts, an n8n instance and a Git branch:
 * The n8n instance is where you build and run workflows.
 * The Git branch stores copies of the workflows, as well as tags, and variable and credential stubs.
 
-n8n doesn't sync credentials and variable values with Git. You must set up the credentials and variable values manually when setting up a new instance. For more information, refer to [Push and pull | What gets committed](/source-control-environments/using/push-pull.md#what-gets-committed) and [Manage variables](/source-control-environments/using/manage-variables.md).
+n8n doesn't sync credentials and variable values with Git. You must set up the credentials and variable values manually when setting up a new instance. For more information, refer to [Push and pull | What gets committed](/source-control-environments/using/push-pull.md#what-gets-committed).
 
 How you copy work between environments depends on your branch and n8n instance configuration:
 

docs/source-control-environments/using/index.md

@@ -13,4 +13,3 @@ hide:
 
 * [Push and pull](/source-control-environments/using/push-pull.md): Send work to Git, and fetch work from Git to your instance. Understand what gets committed, and how n8n handles merge conflicts.
 * [Copy work between environments](/source-control-environments/using/copy-work.md): How to copy work between different n8n instances.
-* [Manage variables](/source-control-environments/using/manage-variables.md): Manage variable values using the n8n API and source control.

docs/source-control-environments/using/push-pull.md

@@ -64,8 +64,6 @@ n8n commits the following to Git:
 * Projects
 * Folders
 
-You can programmatically [Manage variables](/source-control-environments/using/manage-variables.md) using the n8n API.
-
 ## Merge behaviors and conflicts
 
 n8n's implementation of source control is opinionated. It resolves merge conflicts for credentials and variables automatically. n8n can't detect conflicts on workflows.

nav.yml

@@ -142,7 +142,6 @@ nav:
           - source-control-environments/using/index.md
           - Push and pull: source-control-environments/using/push-pull.md
           - Copy work between environments: source-control-environments/using/copy-work.md
-          - Manage variables: source-control-environments/using/manage-variables.md
         - "Tutorial: Create environments with source control": source-control-environments/create-environments.md
       - External secrets: external-secrets.md
       - Log streaming: log-streaming.md