cd-repository-configure

You can scope CD repository changes by analyzing CI file diffs from specific PRs or commit ranges to generate a minimal, precise repository.config filter for deployment. This excludes platform update noise by default.

Restore mode selection determines whether to use Create or CreateUpdate by analyzing CI .xml file history. New files trigger Create mode, while modified files trigger CreateUpdate, optimizing both deployment performance and safety.

Update-only noise is suppressed by classifying and excluding Xperience platform or package update CI churn by default. The system provides clear reporting so you can manually opt in to include these changes when needed.

Yes, you can provide the folder containing cd-repository-context.json along with target PR numbers. The system collects changed CI paths, maps them to CD object types, and updates the configuration with minimal allowlists.

The cd-repository-context.json file requires v2 syntax validation before processing CI repository changes. This validation ensures accurate mapping of CI paths to CD object types and correct restore mode determination.

Yes, deployment package export is supported by optionally running a repository export script. This helps verify that the generated deployment package contains the expected scoped CD objects based on your filter configuration.