Additional configuration among the user interface and the standard ruleset files can be done through
.codeac.yml. This allows you to achieve custom behavior of Codeac per each repository tailored to your projects needs.
Taking your issues seriously is very beneficial in long term to keep your project nice and clean. By adding a small configuration to your repository you can leverage a visual and functional threshold in Codeac. Visit the Issue Thresholds documentation page for more details.
Codeac has bunch of tools enabled by default for each repository. It simplifies the initial repository setup and delivers practical results out of the box. However, sometimes you don't want to run specific analysis on your special project on purpose. You can simply switch the boolean flag in the
.codeac.yml for the irrelevant tool and Codeac will not follow it's default behavior.
Here is the default configuration with all the possible tools listed. You can overwrite it with your own variant of the config file placed in the root of your repository.
version: '1' tools: bandit: enabled: true detekt: enabled: true eslint: enabled: true ethlint: enabled: true hadolint: enabled: true npmAudit: enabled: true phpmd: enabled: true pylint: enabled: true revive: enabled: true rubocop: enabled: true scsslint: enabled: true tfsec: enabled: true tslint: enabled: true