Supply a public Git repository and branch for a PD DigitalOcean App Platform service. Saving the source can start the first app deployment or replace the source of an existing app.

Prepare the source

Use a public Git clone URL over HTTPS and confirm the branch you intend to deploy exists. The module’s input format check does not prove that DigitalOcean can fetch or build the repository. Do not paste repository passwords, access tokens or private clone credentials into this field.

This workflow creates one web-service component. Prepare code compatible with App Platform’s build and runtime requirements; this source form does not expose every setting available in the provider’s full app specification.

Set the repository and branch

1. Open the service page and its Overview in the client area for the intended app service.
2. Open the Change source form.
3. Enter the public HTTPS repository URL and set the branch explicitly. For a first Git source, an omitted branch falls back to main; when changing a Git source, a blank branch can retain the service’s previous branch instead.
4. Review the service and source, then submit the source form when ready. This changes a live app when it already has a source, and the first submission can create the provider app.
5. Read the response, then follow the service’s state and Activity until the requested deployment has an outcome.

Verify the requested version

A message saying the source was saved means the build/deployment was requested. After it becomes live, open the service’s live URL and confirm the expected application version. A previous version can remain available while the new deployment builds, and can still be serving after a failed rollout.

If the source form is unavailable, check the service’s activation/suspension state and whether source changes are enabled on the offering. Review the saved service controls before requesting another deployment.

For invalid input, check the HTTPS URL and branch format. For a later build or deployment failure, check public repository access, the intended branch and application compatibility. A repeatedly clicked Deploy does not repair a failed build. If the outcome is uncertain, inspect the latest requested operation before submitting again.

Do not include private repository credentials, provider tokens or sensitive code.

See the PD DigitalOcean App Platform WHMCS guide for related setup, or explore PD DigitalOcean App Platform.