Scrutinizer automatically infers a configuration for your project which works well to get you started in most circumstances. When it doesn?t, you can adjust its behavior using configuration.
We recommend using a
.scrutinizer.yml file for test related configuration that is placed in your repository. For
analysis configuration or sensitive environment variables, we recommend to keep the configuration on our website
(see our configuration best practices).
If you are just getting started, check out our language guides:
Each configuration consists of four main sections:
|build:||Hosts all your test and deployment configuration.|
|filter:||Defines which files to analyze.|
|checks:||Allows to customize how your code is analyzed.|
|coding_style:||Defines how your code should generally look like.|