Confirm the Git extension and required permissions are available. Prepare a repository without production secrets, identify its release branch and public directory, and take a recoverable backup. Use a dedicated read-only deploy credential for a private repository where possible.

1. Open the domain Git tool and add the remote repository using its verified URL. Configure the required key or credential without placing secrets in a public repository or support message.
2. Choose the intended branch and deployment directory. Check that this location will not overwrite another application or expose private project files.
3. Select manual deployment for the first release. Fetch the repository and inspect the reported commit before publishing it.
4. Configure only the required deployment actions, such as a tested dependency-install or build command. Treat hooks and package scripts as executable code from a trusted project.
5. Deploy during a controlled window, then check the application. Enable automatic deployment or a webhook only after the manual process and recovery procedure work reliably.

Confirm the expected commit or release is live, assets load and application data remains intact. Check that writable uploads and secrets are stored where future deployments will preserve them. Test any build output rather than assuming the source repository is directly web-ready.

For authentication errors, check repository access and the specific deploy key. For build failure, inspect the command runtime and logs before retrying. Redeploying an older code commit does not reverse a database migration or recover overwritten uploads. Keep a separate application recovery plan for those changes.

• Changing a Plesk website document root safely
• Installing PHP application dependencies with Plesk Composer
• Configuring a Node.js application with the Plesk extension
• Creating and downloading a full subscription backup in Plesk

• Plesk: Deploying Content Using Git
• Plesk: Git Git Repositories