1 ##########################################################################################
2 # Customize file classifications. #
3 # Results from files under any classifier will be excluded from LGTM #
5 ##########################################################################################
7 ##########################################################################################
8 # Use the `path_classifiers` block to define changes to the default classification of #
10 ##########################################################################################
17 # Override LGTM's default classification of test files by excluding all files.
19 # Classify all files in the top-level directories test/ and testing/ as test code.
22 # Classify all files with suffix `.Test.py` as test code.
26 # The default behavior is to tag all files created during the
27 # build as `generated`. Results are hidden for generated code. You can tag
28 # further files as being generated by adding them to the `generated` section.
31 # By default, all files not checked into the repository are considered to be
33 # The default behavior is to tag library code as `library`. Results are hidden
34 # for library code. You can tag further files as being library code by adding them
35 # to the `library` section.
37 - exclude: path/to/libary/code/**/*.c
38 # The default behavior is to tag template files as `template`. Results are hidden
39 # for template files. You can tag further files as being template files by adding
40 # them to the `template` section.
43 # Define your own category, for example: 'some_custom_category'.
48 #########################################################################################
49 # Define changes to the default code extraction process. #
50 # Each block configures the extraction of a single language, and modifies actions in a #
51 # named step. Every named step includes automatic default actions, #
52 # except for the 'prepare' step. The steps are performed in the following sequence: #
55 # configure (C/C++ only) #
56 # python_setup (Python only) #
59 ##########################################################################################
61 #########################################################################################
62 # Environment variables available to the steps: #
63 #########################################################################################
66 # The root of the source tree.
68 # An existing (initially empty) folder outside the source tree.
69 # Used for temporary download and setup commands.
71 #########################################################################################
72 # Use the extraction block to define changes to the default code extraction process #
73 # for one or more languages. The settings for each language are defined in a child #
74 # block, with one or more steps. #
75 #########################################################################################
79 # The `prepare` step exists for customization on LGTM.com only.
83 # Add an `after-prepare` step if you need to run commands after the prepare step.
84 # Each command should be listed on a separate line.
86 - export PATH=$LGTM_WORKSPACE/tools:$PATH
87 # The `index` step extracts information from the files in the codebase.
89 # Specify a list of files and folders to extract.
90 # Default: The project root directory.
93 # Specify a list of files and folders to exclude from extraction.
95 - SCons/Tool/docbook/docbook-xsl-1.76.1
97 # Define settings for Python analysis
98 ######################################
100 # The `prepare` step exists for customization on LGTM.com only.
102 # # The `packages` section is valid for LGTM.com only. It names packages to
104 # packages: libpng-dev
105 # This step is useful for Python analysis where you want to prepare the
106 # environment for the `python_setup` step without changing the default behavior
109 - export PATH=$LGTM_WORKSPACE/tools:$PATH
110 # This sets up the Python interpreter and virtual environment, ready for the
111 # `index` step to extract the codebase.
113 # Specify packages that should NOT be installed despite being mentioned in the
114 # requirements.txt file.
115 # Default: no package marked for exclusion.
116 exclude_requirements:
123 # Specify a list of pip packages to install.
124 # If any of these packages cannot be installed, the extraction will fail.
127 # Specify a list of requirements text files to use to set up the environment,
128 # or false for none. Default: any requirements.txt, test-requirements.txt,
129 # and similarly named files identified in the codebase are used.
131 - required-packages.txt
132 # Specify a setup.py file to use to set up the environment, or false for none.
133 # Default: any setup.py files identified in the codebase are used in preference
134 # to any requirements text files.
135 #setup_py: new-setup.py