Our engines-based analysis lets you configure your analysis via a
.codeclimate.yml file in the root of your repository. As shown in the sample file below, the 3 major nodes include:
Issues in files not listed in either the ratings OR exclude_paths nodes will be reported, but will not count toward your repo's overall GPA.
In addition, Code Climate also honors the configuration files of the underlying native static analysis tools, such as .rubocop.yml, and .eslintrc.*.
If you haven't committed a .codeclimate.yml (or other tool-specific config files needed for analysis), you can find the inferred settings by heading to your repo's individual page, and append analysis_config to the URL. Example: https://codeclimate.com/repos/592dd25fc6ce3f0266000383/analysis_config
For configuration of specific engines, please see the support doc for that engine.
For information on configuring specific aspects of your analysis, please see the following docs:
Please see the example
.codeclimate.yml below, that is configured for our Classic analysis.
For more information on how our engines-based analysis compares to our Classic analysis, please see our doc!