Add 'reuse lint' to pre-commit checks #152
jafingerhuttest.yml
on: pull_request
Validate that all files have copyright and license info
13s
test
1m 31s
Annotations
1 error and 5 warnings
|
Validate that all files have copyright and license info
Process completed with exit code 1.
|
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile.dev#L11
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L31
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L30
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L8
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L7
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
p4lang~p4runtime-shell~JPMNE9.dockerbuild
|
35.9 KB |
sha256:8a10c2e28a31f64b562543e6223fb4f7842d893c457ce53fcff87fe873eacfdb
|
|
|
p4lang~p4runtime-shell~MRBLNE.dockerbuild
|
45.1 KB |
sha256:422bc3c6c1b480078177f23c9c3e52e15bfbc969ed4e074ae19bf1e7b1086b30
|
|