Disable FS Pipeline Quality Check for private GitHub Repo for FE pipeline | Community
Skip to main content
K
kevin_vasseure_d
New Member
November 3, 2025
Investigating

Disable FS Pipeline Quality Check for private GitHub Repo for FE pipeline

  • November 3, 2025
  • 3 replies
  • 102 views
Request for Feature Enhancement (RFE) Summary: When using private GitHub repo for our AEM code on Cloud Manager it always triggers FS code quality pipeline, even if the repo is actually meant for FE pipeline.
Use-case: Use private github repo in cloud manager for FE pipeline.
Current/Experienced Behavior: For each pull request, a full stack code quality pipeline is created automatically.
Improved/Expected Behavior: Add the possibility to disable that check when not relevant, in that case for FE only projects.
Environment Details (AEM version/service pack, any other specifics if applicable): AEM as cloud service
Customer-name/Organization name: Danone
Screenshot (if applicable):  
Code package (if applicable):  

    3 replies

    I
    Adobe Employee
    imicuAdobe Employee
    Adobe Employee
    February 19, 2026

    Further explanation from Kevin on this idea:

    We're slowy migrating our AEM repositories from:
    - github repo mirroring to cloudmanager hosted repo 
    to 
    - private github repositories referenced in cloud-manager

    This is working great, excepts that any PR on github creates a code-quality pipeline.
    This is great for repos that are running fullstack pipelines, but useless for repo that are deployed with frontend pipelines. Everything is green because maven build acutally does nothing.


    Is there a way to disable the build-check on PR for certains repos, with a config file for exemple cf https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/managing-code/github-check-config ?
    Or add a build-check on npm run build instead ?

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      March 11, 2026

      Thanks for proposing this idea. This has been reported to the engineering under the internal reference SITES-41695. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira’s status.

      Kautuk Sahni
        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        March 11, 2026
        New→Investigating
        Kautuk Sahni
        Terms & ConditionsAccessibility statement

        Loading footer...