GitHub Actions CI guide
Four-step integration: required CI workflow, optional CoreAnalyzer configuration.
Requirements
- A
COREDEVPRO_LICENCEsecret containing only the CI licence issued on request - Repository permission to create secrets and commit the workflow
Steps
1
Create the secret
Settings → Secrets and variables → Actions → New repository secret
Settings → Secrets and variables → Actions → New repository secret
NAME: COREDEVPRO_LICENCE VALUE: <your_key>2
Add the workflow
• Download the verified workflow, then save it as
• Download the optional configuration only when scope or thresholds need adjustment.
• Download the verified workflow, then save it as
.github/workflows/coredevpro-ci.yml.• Download the optional configuration only when scope or thresholds need adjustment.
Keep the licence in the repository secret. The CLI identifies the repository from the checkout Git remote.
3
Review the scope, then configure only if needed
Keep the defaults when the scope is correct. In an optional
Keep the defaults when the scope is correct. In an optional
coredevpro_config.yml, limit changes to useful thresholds and explicit exclusions:- Duplication:
duplicate_thresholdwithmin_linesandmin_characters - Files:
ignore_dirsandignore_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
Run the workflow or push a commit. The
coredevpro-report artifact contains the native coredevpro-report.cdp report. The workflow runs on every branch and preserves the report when a quality gate fails.If the job fails, read the exact CLI message, then check the licence secret, project rights, quota and connectivity to CoreDevPro.
Finish
→
Download and unzip the artifact, then import
coredevpro-report.cdp, the optional report.json export or coredevpro-report.encrypted.cdp in CoreAnalyzer through Import a JSON/CDP report.