Most administrators find it helpful to define a global project configuration with default settings for all projects. These can then be overridden, where necessary, by individual project configurations. For detailed information about the precedence of different configuration files, see lgtm.yml configuration file in the user help.
To add or edit a global project configuration:
Code analysisadministration page.
Scroll down to the Default project configuration section.
Any existing global project configuration is displayed in the editable text box.
Edit the configuration, or add one, as required, using the YAML serialization language.
The configuration specified here supports exactly the same options as the lgtm.yml file.
Click Save to save your changes.
Alternatively, you can define a global project configuration from the command line by using the
set-project-config action of the
lgtm-cli command. For more information, see set-project-config.
How soon do changes take effect?
The changes take effect as follows:
- Showing/hiding queries—updated data served to users immediately.
- File classification changes—updated data served to users immediately.
- Extraction changes—all analysis jobs created after you've saved the changes will use the new configuration.
Changes to the global project configuration have no impact on projects that have:
- A configuration defined in the LGTM administration interface (see Overriding the global project configuration).
lgtm.ymlconfiguration file stored in the repository.
Only one configuration is considered—that is, configuration settings do not cascade upwards or downwards between the global, project-specific (administration-level), and project-specific (in-repository) configurations. If there is an
lgtm.yml file in the repository, this is used. If this is not found, LGTM looks for a project-specific configuration defined at the administration level. If that is not found, LGTM looks for a global project configuration.