Historically, CircleCI users have been limited to setting up validation systems that only worked within the scope of a single repository.
If a pipeline’s YML config was stored in Repo A, that pipeline could only be triggered from events on Repo A (or from a Custom Webhook). This has left many customers unable to set up the validation system that they want.
We have launched additional enhancements to pipeline and trigger configuration, which will enable customers to build any validation setup that they need.
Read more on our community forum.