Configuration Pipelines to support external github repository

[#1]

Request for Feature Enhancement (RFE) Summary:	Currently we are not able to configure external github repositories to a Configuration deployment pipelines. When we add non-adobe github repo, it throws error  `An external repository is not yet supported for this type of pipeline.`
Use-case:	We were migrating from internal TFS repo to enterprise github repository. We to point other pipelines: Code Quality, FullStack, Front End pipelines to external Git. Just the configuration deployment pipeline alone is blocked. Sounds like temporary limitation, it is intentionally blocked.
Current/Experienced Behavior:	When changing repository to external non-adobe, it is throwing error
Improved/Expected Behavior:	Configuration pipeline should allow external non-adobe github repositories
Environment Details (AEM version/service pack, any other specifics if applicable):	2025.3.20133.20250325T063357Z
Customer-name/Organization name:	SouthernGlazers
Screenshot (if applicable):
Code package (if applicable):

[#2]

Hi @sarav_prakash ,

You can use repository mirroring to mirror your external GitHub repository to an internal supported repository and then configure your configuration deployment pipeline to use the mirrored repository.

To keep things in sync, you can automate the mirroring process so the internal repository always reflects the latest changes from the external GitHub repository.

Regards,

Lavish Vasuja

[#3]

Correct @lavishvasuja . Thats exactly what we did. Created a github action that ll fetch from origin and push into mirror. We have worked around and solved. But asking if adobe can support ootb instead of bandages.