Findings
5 pages filed under Quality › findings. A term is a word of the business with its definition, its aliases and the words it relates to.
| Term | aliases | First line | Links |
|---|---|---|---|
| Build log | build.log.json, log | The file build.log.json the build writes next to the site: its summary (sources, files, entities per type, links per method, keyword pages and expressions under the threshold, twin resources, the decisions of the lock applied, findings per severity and per check, the contracts imported) and every finding, sorted by check, source, path, line and message. Its findings array is the same as the one embedded in the model, and its only timestamp is its at field. The log is written before the verdict of build.fail_on, so a failing build still leaves it for inspection. | 67 |
| Finding | constat, diagnostic | The result of a check on an entity, a link or a file: an identifier, a severity, a file and line, a message and a remediation. A content anomaly becomes a finding, never a crash. The build fails only when the configuration says so; the linter fails from the severity it is told to fail on. | 150 |
| Forge report | SARIF log, JUnit report, lint report | The report the linter writes for a forge with --format: a SARIF log that GitHub code scanning shows in the margin of the diff, on the file and line of each finding; a JUnit report that a GitLab merge request lists as failed tests with the message, the remediation and the page of each; or JSON, which also names the scope, the checks that ran and whether the global scope was degraded. Every form carries the same findings as the text output, and --output writes it to a file, the only file the linter ever writes. | 33 |
| Remediation | how to fix | The sentence every finding carries saying what to change: add the note, fix the path, declare the domain. It comes from the catalogue of the check, the same for the build and the linter, and every finding line ends with the address of the documentation page of the check, whose "How to fix" section says more. The JUnit report shows the remediation with the message so that a merge request reads it without opening the page. | 48 |
| Severity | severity level | What a finding weighs: error, warning or info, the prefix of its check identifier (E-, W-, I-). Every check has a default severity in the catalogue; a project overrides it under checks: of the configuration, a repository under checks: of its concordance-lint.yaml, and a check can be disabled the same way. The build fails according to build.fail_on, on errors by default; the linter fails from the severity --fail-on names, error by default. | 94 |
5 findings of 5 — pagination by twenty. The Links column counts the related pages, which brings the most central findings of the journey to the top.