Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.

Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.

Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.

Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.

Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.

Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.

Name of a workflow file must match the name of the main struct in it (without the PWG prefix). (Class implementation files should be in "Core" directories.)

Specify task name only when it cannot be derived from the struct name. Only append to the default name.

Device names filter-eoi and filter-eo-i generated from the specified task name filter-eoi and from the struct name filterEoI, respectively, differ in hyphenation. Consider fixing capitalisation of the struct name to FilterEoi and removing TaskName.

Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: thollander/actions-comment-pull-request@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

To tolerate certain issues in a directory, add a line with the test name in "o2linter_config".