Change Analysis showing PR results with linter badges for Duplicates, Compliance, Architecture, and Code Analyzer
Change Analysis automatically reviews every pull request for code quality issues before it is merged. It runs four linters against the PR diff — not the entire repository — so results are focused on what actually changed.
What gets checked
Each PR is analyzed by four linters. Results appear as colored badges on each PR row — green for pass, orange for warnings, red for failures.
Duplicates
Duplicate Analysis showing aliased package detection with file locations
Detects duplicate metadata components across your packages. For example, if the same CustomLabel appears in multiple packages, the Duplicates linter flags it with the exact file paths. This prevents conflicts during deployment where one package's version of a component overwrites another.
Compliance
Compliance Check showing rules checked, violations found, and specific warnings with file locations and rule details
Checks your changes against a set of compliance rules. The report shows how many rules were checked, how many violations were found, and the specific warnings with file locations and rule descriptions. For example, flagging System.debug statements that should be removed before production.
Code Analyzer
Code Analyzer results showing engine details, rules checked, issues found, and specific notes with file locations
Runs Salesforce Code Analyzer (PMD and other engines) against the changed files. Results are presented in SARIF format with the engine used, rules checked, files analyzed, execution time, and specific issues with file locations and line numbers.
Architecture
Architecture Analysis showing AI-powered insights about coupling, dependency concerns, and design issues
AI-powered analysis that evaluates the architectural impact of your changes. It identifies concerns like implicit coupling between packages, dependency violations, backwards compatibility risks, and design issues. Each insight includes the specific files involved and an explanation of why it matters.
How it works
Change Analysis is triggered automatically when a PR is opened or updated. codev's workflow engine:
Clones the repository at the merge ref
Computes the diff between the PR and the base branch
Runs each linter against only the changed files
Publishes results to the server and creates a check run on the PR in GitHub
The whole process typically completes in under a minute.
Configuring analysis
Click Workflow Settings on the Change Analysis page to enable or disable the PR analysis workflow.
You can also configure which linters are active and which should cause a PR check to fail. This is configured per branch pattern — for example, you might exclude architecture analysis on feature branches but enforce compliance checks on release branches.
Click any PR row to see the full analysis detail. The left sidebar shows PR info (branch, target, commit) and linter result badges. The main content area has tabs for each linter — click through to see the specific findings.
The Run History section at the bottom of the sidebar shows previous analysis runs for the same PR, so you can see if issues were introduced or fixed across commits.
