Skip to content

Add 'reuse lint' to pre-commit checks #153

Add 'reuse lint' to pre-commit checks

Add 'reuse lint' to pre-commit checks #153

Triggered via pull request April 24, 2026 01:05
Status Success
Total duration 1m 13s
Artifacts 2

test.yml

on: pull_request
Validate that all files have copyright and license info
13s
Validate that all files have copyright and license info
test
1m 10s
test
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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~BATW4I.dockerbuild
44.3 KB
sha256:dbc475db352ed463a8826734b37096749538dfc4519b518740082f3336a00af4
p4lang~p4runtime-shell~MRL6W7.dockerbuild
34.9 KB
sha256:edede60351562c98b859e2d9330e5aed6b3280238cc4e55e78ee0e9300cb1b24