# Github monorepo build triggers

**URL:** <https://community.codefresh.io/t/github-monorepo-build-triggers/1086>\
**Category:** Pipeline Workflows\
**Created:** [October 4, 2026, 3:48am UTC](https://community.codefresh.io/t/github-monorepo-build-triggers/1086 "2026-10-04T03:48:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![susithapb](https://avatars.discourse-cdn.com/v4/letter/s/b5e925/32.png) [@susithapb](https://community.codefresh.io/u/susithapb)\
**Post date:** [October 4, 2026, 3:48am UTC](https://community.codefresh.io/t/github-monorepo-build-triggers/1086/1 "2026-10-04T03:48:16Z")

</div>

Hello Community,

I’m new to the community and need a favor to design a pipeline for a React UI Monorepo in Github cloud.

We have built a Monorepo with multiple sites in it.  
eg.  
src/

- site\_1
- site\_2
- site\_3

We have already setup a CI and CD pipeline for this Monorepo. Once we push to a site, it’ll run CI and publish a package to the Artifactory. Once a new version is published we won’t to trigger another pipeline related to the site. Meaning, different sites were maintained by different teams and maintains deployment pipelines by themselves. So, when a new version of the package is published to Artifactory, this newer version should deploy to Dev, Stage, etc via the application pipelines.

Please help me to design this by adhering to industry standards.

Thanks!