keel-regression

Code regression scanning is automated by running a CLI command that initiates parallelized scanning across different codebase areas. It identifies potential regressions, eliminates duplicate findings, and automatically generates GitHub issues for fix candidates.

Parallelized code analysis works by distributing the regression scanning process across various predefined areas of the codebase. This area-based parallelism accelerates the analysis and quickly surfaces potential code regressions without redundant checks.

Yes, you can automatically generate GitHub issues directly from code regression findings. The scanning process logs potential fix candidates and routes them through a specified command to create issues, requiring a GitHub integration.

Yes, you need a pre-existing .keel configuration file to perform code regression scanning. This configuration drives the area-based parallelism and defines how the automated analysis identifies and logs potential regressions.

The best way to prevent duplicate GitHub issues during codebase analysis is to use an automated scanning process with built-in deduplication. It removes duplicate findings before generating GitHub issues, ensuring only unique regressions are reported.

Yes, keel regression works directly with Git and GitHub for issue tracking. It integrates with your GitHub repository to automatically generate and route issues for identified code regressions and fix candidates.