Import Repository Files with File Studio Git Deploy
Deploy an HTTPS Git repository into an account folder using File Studio, with default-branch import, replacement behavior and task verification.
Open Tools → Git Deploy. The option appears when the provider enables Git uploads. The server also needs an available executable Git command and network access to the repository. Demo servers block deployment.
Fields and requirements
| Field | Requirement |
|---|---|
| Git Repository URL | Required HTTPS URL ending in .git, such as https://example.com/team/project.git. |
| Deploy To | Required folder within the account; use Browse → Select Folder. The account home itself is rejected. |
Although the panel route's preliminary validator accepts additional schemes, the file-service handler requires HTTPS and a .git suffix. Use that supported form. There is no SSH-key, username/password, branch, tag or commit selector in this dialog. A repository requiring interactive authentication may fail; do not embed credentials in the URL.
Deploy
- Choose a separate project or staging folder and preserve existing destination data.
- Open Git Deploy, enter the repository URL and select Deploy To.
- Click Deploy and monitor the job in Tasks.
- After completion, refresh the destination and check the imported files.
The backend makes a shallow clone of the repository's default branch, removes the clone's .git metadata, then imports its files into the destination. This is a file import, not a working checkout with pull/update controls. The destination can be created if missing.
Deployment can overwrite files
The import merges into the chosen destination with overwrite enabled and adjusts ownership and modes. There is no overwrite checkbox or automatic rollback. Do not deploy over unpreserved live content.
A completed import does not install dependencies, build assets, run migrations or configure a website runtime. Follow the relevant application deployment guide. On failure, inspect the task and destination before retrying; temporary clone space, disk limits, network errors and repository access can prevent completion.