Skip to content

Community: adding code of conduct page #940

Community: adding code of conduct page

Community: adding code of conduct page #940

Triggered via pull request September 18, 2024 23:35
Status Success
Total duration 1m 52s
Artifacts 3

build-docs.yml

on: pull_request
Matrix: checks
Matrix: cloudfront
Matrix: docker
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
checks (community, community)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
checks (docs, docs)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L20
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#L20
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#L20
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
anoma~namada-docs~AQLSO6.dockerbuild
19.6 KB
anoma~namada-docs~ET58PG.dockerbuild
21.4 KB
anoma~namada-docs~IZ6ONB.dockerbuild
21.2 KB