GitHub Actions CI guide

Four-step integration: required CI workflow, optional CoreAnalyzer configuration.
Requirements
Steps
1
Create the secret
Settings → Secrets and variables → Actions → New repository secret
NAME: COREDEVPRO_LICENCE VALUE: <your_key>
2
Add the workflow
• Add .github/workflows/coredevpro-ci.yml supplied by CoreDevPro.
• Add coredevpro_config.yml at the project root only when scope or thresholds need adjustment.
Keep the licence in the repository secret. The workflow fills X-REPO from GITHUB_REPOSITORY.
3
Review the scope, then configure only if needed
Keep the defaults when the scope is correct. In an optional coredevpro_config.yml, limit changes to useful thresholds and explicit exclusions:
  • Duplication: duplicate_threshold with min_lines and min_characters
  • Files: ignore_dirs and ignore_files
  • CoreAnalyzer handles native technical exclusions automatically.
  • Tests can provide usage evidence; do not exclude them by default.
4
Run and verify
Run the workflow or push a commit. The coredevpro-report artifact contains report.json by default. For CLI workflows, use --output coredevpro-report.signed.cdp --cdp-email user@company.com or --output coredevpro-report.encrypted.cdp --cdp-email user@company.com --cdp-password-env COREDEVPRO_CDP_PASSWORD when those formats are enabled.
If the job fails, check the licence secret, archive size and connectivity to CoreDevPro.
Finish
→
Download and unzip the artifact, then import report.json, coredevpro-report.signed.cdp or coredevpro-report.encrypted.cdp in CoreAnalyzer through Import a JSON/CDP report.