DocumentationAEMUser Guide

Configure an Edge Delivery site to use an external Git repository

Last update: June 23, 2026
  • Applies to:
  • Experience Manager as a Cloud Service

CREATED FOR:

  • Admin
  • Developer

To pull code from any private Git repository already onboarded in Cloud Manager, you can configure your Edge Delivery site.

To use an external Git repository, configure an Edge Delivery site:

  1. Sign in to Cloud Manager at experience.adobe.com.

    1. In the Quick access section, click Experience Manager.
    2. In the left panel, click Cloud Manager.

  2. In Cloud Manager, near the upper-right corner of the page, select an organization that you want to use.

  3. On the My Programs console, select the program with Edge Delivery Services configured. Select the program where you want to configure an Edge Delivery site to use an external Git repository.

  4. In the left rail, under the Program heading, click Overview icon .

  5. On the Program Overview page, click the Edge Delivery tab.

  6. In the Edge Delivery sites table, click More icon at the end of a row whose site you want to configure to use an external repo, then click Bring your own Git.

  7. In the Bring your own Git dialog box, in the Repository Name drop-down list, choose a Git repo with READY status, then click Confirm.

    Cloud Manager returns a one-time secret token. If you reconfigure the site, Cloud Manager generates a new secret token.

  8. Copy the token and add it to the site configuration in helix-admin, as described in the BYO Git guide.

  9. In Cloud Manager, click More icon at the end of a row whose site you configured to use an external repo, then click Sync code.

  10. Pick the branch to sync, and click Sync.

Each commit on any branch now triggers an automatic sync. Use Sync code again whenever a full manual sync is required.

Authenticate git clone requests authenticate-git-clone-requests

You can clone your Bring Your Own Git repository from Cloud Manager using either an IMS token or the byogit secret that Cloud Manager generates when you configure the site. Both credentials authenticate against the clone endpoint, so you can use the secret that helix-admin already stores for Edge Delivery Services code sync.

The clone endpoint accepts the credential in the Authorization header. Cloud Manager validates the byogit secret against the value stored for that repository. Requests that include neither a valid IMS token nor a valid byogit secret return a 401 response.

NOTE
Existing IMS-authenticated clone workflows are unaffected. The byogit secret is an additional option, not a replacement.

To clone the repository with the byogit secret:

  1. Copy the secret that Cloud Manager returns when you configure the site.

  2. Run your clone command, and pass the secret in the Authorization header.

    git -c http.extraHeader="Authorization: <byogit-secret>" clone https://cm-repo.adobe.io/api/program/<program-id>/repository/<repository-id>.git

    Replace <byogit-secret> with the secret from Cloud Manager, and replace <program-id> and <repository-id> with the values from your program.

recommendation-more-help
experience-manager-cloud-service-help-main-toc