Reference B: Code Criteria references and examples
Examples and reference rules for Code Criteria grouping, unification, and scope.
Use these examples to understand how grouping, unification, and scope filters affect generated applications.
For toggle dependencies and deployment behavior, see Reference A: Code Criteria grouping and unification.
Grouping and unification examples
Merge within a provider
A Criteria targets GitHub with Group by set to Repository. Two projects in acme-eng expose repositories named payments-api.
GitHub
acme-eng
checkout
payments-api
GitHub
acme-eng
billing
payments-api
Off
Two separate payments-api applications, one for each source repository.
On
One payments-api application containing both repositories.
Unify across providers
A Criteria targets GitHub and GitLab with Group by set to Repository. Both providers host payments-api.
GitHub
acme-eng
payments-api
GitLab
acme-platform
payments-api
Off
Off
Two applications: payments-api_GitHub and payments-api_GitLab.
On
Off
The same two applications. Merging operates only within each provider.
On
On
One payments-api_GitHub_GitLab application spanning both providers.
Multi-provider scope filtering
A Criteria targets three provider tabs. Each tab has its own grouping level and filters.
GitHub — Group by: Organization. Organization Name Contains
payments.GitLab — Group by: Repository. Repository Name Equal
api-gateway.Bitbucket — Group by: Project. No filters.
The final scope is the union of all tabs.
GitHub
Every repository under organizations containing payments, grouped per organization
GitLab
Every repository named api-gateway, grouped per repository
Bitbucket
Every connected repository, grouped per project
The result sets are added together. They do not intersect. The unfiltered Bitbucket tab includes all connected Bitbucket projects.
If unification is enabled, identically named applications then merge according to Reference A: Code Criteria grouping and unification.
Last updated
Was this helpful?
