summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKlaus Aehlig <klaus.aehlig@huawei.com>2024-10-25 18:09:06 +0200
committerKlaus Aehlig <klaus.aehlig@huawei.com>2024-10-25 18:09:06 +0200
commitb34bb0cb44cd1c5cd432dc8f4fe9968b599b743a (patch)
tree89f031f81cb6ab65ce34d6b1e0bf2aacea3713de
parent1e04e4002e770148993da3ffcf1735caa4b2df4e (diff)
downloadrules-cc-b34bb0cb44cd1c5cd432dc8f4fe9968b599b743a.tar.gz
Update derived files
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 3fe08db..8814784 100644
--- a/README.md
+++ b/README.md
@@ -582,7 +582,7 @@ Run a given linter on the lint information provided by the given targets.
| Field | Description |
| ----- | ----------- |
-| `"linter"` | Single artifact running the lint checks. This program is invoked with - argv`[1]` the file to lint, and - argv`[2:]` the original command line. This invocation happens in an environment with - CONFIG pointing to the directory with all the artifacts given by the field `"config"`, and - OUT pointing to a directory to which files with the lint result can be written. It is supposed to indicate by the exit code whether the file to lint complies with the given linting policy, with 0 meaning compliant. Stdout and stderr, as well as the directory $`{OUT}` can be used to provide additional information. |
+| `"linter"` | Single artifact running the lint checks. This program is invoked with - argv`[1]` the file to lint, and - argv`[2:]` the original command line. This invocation happens in an environment with - CONFIG pointing to the directory with all the artifacts given by the field `"config"`, and - OUT pointing to a directory to which files with the lint result can be written. - META pointing to a json file contaning - at key `"direct deps artifact names"` a list of all input artifacts that come from the target itself or are runfiles of a direct dependency. It is supposed to indicate by the exit code whether the file to lint complies with the given linting policy, with 0 meaning compliant. Stdout and stderr, as well as the directory $`{OUT}` can be used to provide additional information. |
| `"config"` | Any configuration or other files needed by the linter. |
| `"summarizer"` | Single artifact generating a summary of the individual lint results. It will be called in a directory where all subdirectories except . and .. represent the results of the individual lint actions. Those are given as - a file `"result"` with content `"PASS"` if and only if the lint action exited 0, - files `"stdout"` and `"stderr"` with stdout and stderr of the lint action, and - a directory `"out"` with the additional information provided by the lint action. The summarizer is required to indicate the overall result by the exit code, produce a human-readable summary on stdout, and optionally additional information in the directory $`{OUT}`. |