hostinger-api-mcp 1.60.0 → 1.60.2

package/src/core/tools/hosting.ts

@@ -1410,6 +1410,213 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_getGitAutoDeploymentSettingsV1",
+    "title": "Get Git auto-deployment settings",
+    "annotations": {
+      "title": "Get Git auto-deployment settings",
+      "readOnlyHint": true,
+      "destructiveHint": false
+    },
+    "description": "Returns the Git auto-deployment settings of the website: which repository and branch deploy\ninto which directory, and whether pushes trigger a deployment. `is_enabled` false keeps the\nrepository link but ignores pushes.\n\nWhen the website has no auto-deployment configured every field is null. Save settings with\n`Update Git auto-deployment settings`.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/git/auto-deployments/settings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_updateGitAutoDeploymentSettingsV1",
+    "title": "Update Git auto-deployment settings",
+    "annotations": {
+      "title": "Update Git auto-deployment settings",
+      "readOnlyHint": false,
+      "destructiveHint": true,
+      "idempotentHint": true
+    },
+    "description": "Creates or replaces the Git auto-deployment settings of the website: repository, branch, the\ndirectory under the document root to deploy into, and `is_enabled`. Send the full set;\n`is_enabled` defaults to true and `directory` to the document root. `installation_uuid` must\nbe an installation from `List Git installations` that belongs to the same customer as the\nwebsite.\n\nFor PHP and static websites, saving with `is_enabled` true deploys the branch right away and\nevery later push to that branch deploys again. For Node.js and Website Builder websites saving\ndoes not clone anything. On a Node.js website start the first deploy with\n`Start Node.js build` using `source_type` `git`; pushes then trigger new builds with the build\nsettings stored for the website.",
+    "method": "PUT",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/git/auto-deployments/settings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "installation_uuid": {
+          "type": "string",
+          "description": "Active Git installation from `List Git installations`"
+        },
+        "owner": {
+          "type": "string",
+          "description": "Repository owner login, as returned by `List Git installation repositories`. GitLab group\npaths use slashes."
+        },
+        "repository": {
+          "type": "string",
+          "description": "Repository name without the .git suffix"
+        },
+        "branch": {
+          "type": "string",
+          "description": "Branch to deploy"
+        },
+        "directory": {
+          "type": "string",
+          "description": "Subdirectory under the website document root to deploy into. Empty, null or omitted means\nthe document root."
+        },
+        "is_enabled": {
+          "type": "boolean",
+          "description": "Whether pushes to the branch deploy automatically"
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "installation_uuid",
+        "owner",
+        "repository",
+        "branch"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_deleteGitAutoDeploymentSettingsV1",
+    "title": "Delete Git auto-deployment settings",
+    "annotations": {
+      "title": "Delete Git auto-deployment settings",
+      "readOnlyHint": false,
+      "destructiveHint": true,
+      "idempotentHint": true
+    },
+    "description": "Removes the Git auto-deployment settings of the website. Files already deployed stay on the\nwebsite; pushes stop deploying until settings are saved again. Succeeds also when nothing is\nconfigured.",
+    "method": "DELETE",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/git/auto-deployments/settings",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_listGitInstallationsV1",
+    "title": "List Git installations",
+    "annotations": {
+      "title": "List Git installations",
+      "readOnlyHint": true,
+      "destructiveHint": false
+    },
+    "description": "Lists the Git provider accounts the customer has connected. Only installations with status\n`active` are returned unless the `status` filter says otherwise.\n\nAn empty list means the customer has no active installation. Check `status=suspended` and\n`status=pending` as well. If there is none at all, a Git provider (GitHub or GitLab) has to be\nconnected once in hPanel (Websites, Manage, Advanced, Git; or Add Website, Node.js Web App,\nImport Git Repository); this endpoint then lists the new installation.\n\nUse `uuid` as the path parameter of `List Git installation repositories`, and as\n`installation_uuid` in `Start Node.js build` with `source_type` `git` and in\n`Update Git auto-deployment settings`.",
+    "method": "GET",
+    "path": "/api/hosting/v1/git/installations",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "provider": {
+          "type": "string",
+          "description": "Filter by Git provider",
+          "enum": [
+            "github",
+            "gitlab",
+            "bitbucket"
+          ]
+        },
+        "status": {
+          "type": "string",
+          "description": "Filter by installation status",
+          "enum": [
+            "pending",
+            "active",
+            "suspended"
+          ]
+        }
+      },
+      "required": []
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_listGitInstallationRepositoriesV1",
+    "title": "List Git installation repositories",
+    "annotations": {
+      "title": "List Git installation repositories",
+      "readOnlyHint": true,
+      "destructiveHint": false
+    },
+    "description": "Lists the repositories the Git installation can access, read live from the provider. Works\nfor github and gitlab installations. Use an active installation: a suspended or pending one\nis still queried and the call fails with whatever the provider answers. The list is cut at\nthe first 500 repositories in the order the provider returns them; when the account has\nmore, name the repository directly instead of searching this list.\n\n`owner`, `name` and a branch (`default_branch` or another one) go into `source_options` of\n`Start Node.js build` or into `Update Git auto-deployment settings`. Returns 404 when the\ninstallation does not belong to the customer. Limited to 10 calls per minute per API client\n(429 above that).",
+    "method": "GET",
+    "path": "/api/hosting/v1/git/installations/{uuid}/repositories",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "uuid": {
+          "type": "string",
+          "description": "Git installation UUID from the List Git installations endpoint"
+        }
+      },
+      "required": [
+        "uuid"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_listNodeJSBuildsV1",
     "title": "List NodeJS builds",
@@ -1475,7 +1682,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Start a Node.js build process using files already present on the website's file storage.\n\nWARNING: on success this overwrites the website's existing contents and cannot be\nundone — verify this is intended before calling this endpoint.\n\nThe `source_type` must be `archive` and `source_options.archive_path` must point to an\nexisting archive file on the server (relative to the website document root).\nUse the `Generate Upload URL` endpoint to obtain credentials and upload the archive first.\n\nTo auto-detect build settings from an archive before starting, first call the\n`Get Node.js Build Settings from Archive` endpoint.\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
+    "description": "Start a Node.js build process using files already present on the website's file storage.\n\nWARNING: on success this overwrites the website's existing contents and cannot be\nundone — verify this is intended before calling this endpoint.\n\nWith `source_type` `archive`, `source_options.archive_path` must point to an existing\narchive file on the server (relative to the website document root). Use the\n`Generate Upload URL` endpoint to obtain credentials and upload the archive first. To\nauto-detect build settings from an archive before starting, first call the\n`Get Node.js Build Settings from Archive` endpoint.\n\nWith `source_type` `git`, `source_options` carries `owner`, `repository`, `branch` and\n`installation_uuid`. Take the installation from `List Git installations` and the owner and\nrepository from `List Git installation repositories`; the branch is cloned at its current\nhead. The installation must belong to the same customer as the website.\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds",
     "inputSchema": {
@@ -1551,18 +1758,35 @@ const tools: OpenApiTool[] = [
         },
         "source_type": {
           "type": "string",
-          "description": "The source type of the files",
+          "description": "Where the files come from: `archive` (an uploaded archive on the website) or `git`\n(a branch of a repository reachable through a Git installation).",
           "enum": [
-            "archive"
+            "archive",
+            "git"
           ]
         },
         "source_options": {
           "type": "object",
-          "description": "Source-specific options",
+          "description": "Source-specific options. For `archive` send `archive_path`. For `git` send `owner`,\n`repository`, `branch` and `installation_uuid`, taken from `List Git installations`\nand `List Git installation repositories`.",
           "properties": {
             "archive_path": {
               "type": "string",
               "description": "The path to the archive file relative to the document root of the vhost (required if source is \"archive\")"
+            },
+            "owner": {
+              "type": "string",
+              "description": "Repository owner login (required if source is \"git\"). GitLab group paths use\nslashes."
+            },
+            "repository": {
+              "type": "string",
+              "description": "Repository name without the .git suffix (required if source is \"git\")"
+            },
+            "branch": {
+              "type": "string",
+              "description": "Branch to build (required if source is \"git\")"
+            },
+            "installation_uuid": {
+              "type": "string",
+              "description": "Git installation used to access the repository (required if source is \"git\")"
             }
           }
         }

package/src/servers/agency-hosting.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.60.2', tools });

package/src/servers/agency-hosting.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.60.2', tools });

package/src/servers/all.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.60.2', tools });

package/src/servers/all.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.60.2', tools });

package/src/servers/billing.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.60.2', tools });

package/src/servers/billing.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.60.2', tools });

package/src/servers/dns.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.60.2', tools });

package/src/servers/dns.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.60.2', tools });

package/src/servers/domains.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.60.2', tools });

package/src/servers/domains.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.60.2', tools });

package/src/servers/ecommerce.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.60.2', tools });

package/src/servers/ecommerce.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.60.2', tools });

package/src/servers/horizons.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.60.2', tools });

package/src/servers/horizons.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.60.2', tools });

package/src/servers/hosting.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.60.2', tools });

package/src/servers/hosting.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.60.2', tools });

package/src/servers/mail.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.60.2', tools });

package/src/servers/mail.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.60.2', tools });

package/src/servers/reach.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.60.2', tools });

package/src/servers/reach.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.60.2', tools });

package/src/servers/vps.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.60.2', tools });

package/src/servers/vps.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.60.2', tools });

package/src/servers/wordpress.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.60.2', tools });

package/src/servers/wordpress.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '1.60.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.60.2', tools });

package/types.d.ts

@@ -3770,6 +3770,149 @@ containing secrets (e.g. credential files) — none of these are returned by thi
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Returns the Git auto-deployment settings of the website: which repository and branch deploy
+into which directory, and whether pushes trigger a deployment. `is_enabled` false keeps the
+repository link but ignores pushes.
+
+When the website has no auto-deployment configured every field is null. Save settings with
+`Update Git auto-deployment settings`.
+   */
+  "hosting_getGitAutoDeploymentSettingsV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Creates or replaces the Git auto-deployment settings of the website: repository, branch, the
+directory under the document root to deploy into, and `is_enabled`. Send the full set;
+`is_enabled` defaults to true and `directory` to the document root. `installation_uuid` must
+be an installation from `List Git installations` that belongs to the same customer as the
+website.
+
+For PHP and static websites, saving with `is_enabled` true deploys the branch right away and
+every later push to that branch deploys again. For Node.js and Website Builder websites saving
+does not clone anything. On a Node.js website start the first deploy with
+`Start Node.js build` using `source_type` `git`; pushes then trigger new builds with the build
+settings stored for the website.
+   */
+  "hosting_updateGitAutoDeploymentSettingsV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Active Git installation from `List Git installations`
+       */
+      installation_uuid: string;
+      /**
+       * Repository owner login, as returned by `List Git installation repositories`. GitLab group
+paths use slashes.
+       */
+      owner: string;
+      /**
+       * Repository name without the .git suffix
+       */
+      repository: string;
+      /**
+       * Branch to deploy
+       */
+      branch: string;
+      /**
+       * Subdirectory under the website document root to deploy into. Empty, null or omitted means
+the document root.
+       */
+      directory?: string;
+      /**
+       * Whether pushes to the branch deploy automatically
+       */
+      is_enabled?: boolean;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Removes the Git auto-deployment settings of the website. Files already deployed stay on the
+website; pushes stop deploying until settings are saved again. Succeeds also when nothing is
+configured.
+   */
+  "hosting_deleteGitAutoDeploymentSettingsV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Lists the Git provider accounts the customer has connected. Only installations with status
+`active` are returned unless the `status` filter says otherwise.
+
+An empty list means the customer has no active installation. Check `status=suspended` and
+`status=pending` as well. If there is none at all, a Git provider (GitHub or GitLab) has to be
+connected once in hPanel (Websites, Manage, Advanced, Git; or Add Website, Node.js Web App,
+Import Git Repository); this endpoint then lists the new installation.
+
+Use `uuid` as the path parameter of `List Git installation repositories`, and as
+`installation_uuid` in `Start Node.js build` with `source_type` `git` and in
+`Update Git auto-deployment settings`.
+   */
+  "hosting_listGitInstallationsV1": {
+    params: {
+      /**
+       * Filter by Git provider
+       */
+      provider?: string;
+      /**
+       * Filter by installation status
+       */
+      status?: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Lists the repositories the Git installation can access, read live from the provider. Works
+for github and gitlab installations. Use an active installation: a suspended or pending one
+is still queried and the call fails with whatever the provider answers. The list is cut at
+the first 500 repositories in the order the provider returns them; when the account has
+more, name the repository directly instead of searching this list.
+
+`owner`, `name` and a branch (`default_branch` or another one) go into `source_options` of
+`Start Node.js build` or into `Update Git auto-deployment settings`. Returns 404 when the
+installation does not belong to the customer. Limited to 10 calls per minute per API client
+(429 above that).
+   */
+  "hosting_listGitInstallationRepositoriesV1": {
+    params: {
+      /**
+       * Git installation UUID from the List Git installations endpoint
+       */
+      uuid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve a paginated list of Node.js build processes for a specific website.
 
@@ -3809,13 +3952,17 @@ Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs`
 WARNING: on success this overwrites the website's existing contents and cannot be
 undone — verify this is intended before calling this endpoint.
 
-The `source_type` must be `archive` and `source_options.archive_path` must point to an
-existing archive file on the server (relative to the website document root).
-Use the `Generate Upload URL` endpoint to obtain credentials and upload the archive first.
-
-To auto-detect build settings from an archive before starting, first call the
+With `source_type` `archive`, `source_options.archive_path` must point to an existing
+archive file on the server (relative to the website document root). Use the
+`Generate Upload URL` endpoint to obtain credentials and upload the archive first. To
+auto-detect build settings from an archive before starting, first call the
 `Get Node.js Build Settings from Archive` endpoint.
 
+With `source_type` `git`, `source_options` carries `owner`, `repository`, `branch` and
+`installation_uuid`. Take the installation from `List Git installations` and the owner and
+repository from `List Git installation repositories`; the branch is cloned at its current
+head. The installation must belong to the same customer as the website.
+
 The returned build `uuid` can be used to poll progress and retrieve logs via
 the `Get Node.js Build Logs` endpoint.
    */
@@ -3858,11 +4005,14 @@ the `Get Node.js Build Logs` endpoint.
        */
       package_manager?: string;
       /**
-       * The source type of the files
+       * Where the files come from: `archive` (an uploaded archive on the website) or `git`
+(a branch of a repository reachable through a Git installation).
        */
       source_type: string;
       /**
-       * Source-specific options
+       * Source-specific options. For `archive` send `archive_path`. For `git` send `owner`,
+`repository`, `branch` and `installation_uuid`, taken from `List Git installations`
+and `List Git installation repositories`.
        */
       source_options: object;
     };