.codeclimate.yml

# This is a sample .codeclimate.yml configured for Engine analysis on Code
# Climate Platform For an overview of the Code Climate Platform, see here:
# http://docs.codeclimate.com/article/300-the-codeclimate-platform

# Under the engines key, you can configure which engines will analyze your repo.
# Each key is an engine name. For each value, you need to specify enabled: true
# to enable the engine as well as any other engines-specific configuration.

# For more details, see here:
# http://docs.codeclimate.com/article/289-configuring-your-repository-via-codeclimate-yml#platform

# For a list of all available engines, see here:
# http://docs.codeclimate.com/article/296-engines-available-engines

engines:
# to turn on an engine, add it here and set enabled to `true`
# to turn off an engine, set enabled to `false` or remove it
  csslint:
    enabled: false
  fixme:
    enabled: false
    config:
      strings:
      - FIXME
      - TODO
  phan:
    enabled: false
    config:
      file_extensions: "php"
      # ignore-undeclared: true
  phpcodesniffer:
    enabled: false
  phpmd:
    enabled: true
  sonar-php:
    enabled: false
    config:
      minimum_severity: critical

# Engines can analyze files and report issues on them, but you can separately
# decide which files will receive ratings based on those issues. This is
# specified by path patterns under the ratings key.

# For more details see here:
# http://docs.codeclimate.com/article/289-configuring-your-repository-via-codeclimate-yml#platform

ratings:
  paths:
  - "**.css"
  - "**.js"
  - "**.php"

# You can globally exclude files from being analyzed by any engine using the
# exclude_paths key.

#languages:
#   PHP: true
#   JavaScript: true

exclude_paths:
- "vendor/*"
- "tests/*"