Skip to content

Initial documentation #391

Initial documentation

Initial documentation #391

Triggered via pull request December 4, 2024 15:46
@arturo-seijasarturo-seijas
synchronize #51
docs
Status Success
Total duration 15m 14s
Artifacts 1

test.yaml

on: pull_request
unit-tests  /  Inclusive naming
14s
unit-tests / Inclusive naming
unit-tests  /  Shell scripts lint
15s
unit-tests / Shell scripts lint
unit-tests  /  Dockerfile lint
6s
unit-tests / Dockerfile lint
unit-tests  /  Lint metadata.yaml
6s
unit-tests / Lint metadata.yaml
unit-tests  /  Lint and unit tests
2m 33s
unit-tests / Lint and unit tests
unit-tests  /  Draft publish docs
34s
unit-tests / Draft publish docs
unit-tests  /  Check license headers
46s
unit-tests / Check license headers
unit-tests  /  Check libraries
23s
unit-tests / Check libraries
unit-tests  /  Style checker
54s
unit-tests / Style checker
unit-tests  /  Required Test Status Checks
5s
unit-tests / Required Test Status Checks
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
unit-tests / Style checker: docs/reference/integrations.md#L1
[vale] reported by reviewdog 🐶 [Canonical.011-Headings-not-followed-by-heading] Avoid stacked headings. There should be content for each heading. Raw Output: {"message": "[Canonical.011-Headings-not-followed-by-heading] Avoid stacked headings. There should be content for each heading.", "location": {"path": "docs/reference/integrations.md", "range": {"start": {"line": 1, "column": 1}}}, "severity": "WARNING"}
unit-tests / Style checker: docs/tutorial/getting-started.md#L1
[vale] reported by reviewdog 🐶 [Canonical.011-Headings-not-followed-by-heading] Avoid stacked headings. There should be content for each heading. Raw Output: {"message": "[Canonical.011-Headings-not-followed-by-heading] Avoid stacked headings. There should be content for each heading.", "location": {"path": "docs/tutorial/getting-started.md", "range": {"start": {"line": 1, "column": 1}}}, "severity": "WARNING"}
unit-tests / Style checker: docs/tutorial/getting-started.md#L38
[vale] reported by reviewdog 🐶 [Canonical.016-No-inline-comments] Avoid inline comments in code blocks. Raw Output: {"message": "[Canonical.016-No-inline-comments] Avoid inline comments in code blocks.", "location": {"path": "docs/tutorial/getting-started.md", "range": {"start": {"line": 38, "column": 1}}}, "severity": "WARNING"}
unit-tests / Style checker: docs/how-to/contribute.md#L1
[vale] reported by reviewdog 🐶 [Canonical.011-Headings-not-followed-by-heading] Avoid stacked headings. There should be content for each heading. Raw Output: {"message": "[Canonical.011-Headings-not-followed-by-heading] Avoid stacked headings. There should be content for each heading.", "location": {"path": "docs/how-to/contribute.md", "range": {"start": {"line": 1, "column": 1}}}, "severity": "WARNING"}
unit-tests / Style checker: docs/how-to/contribute.md#L25
[vale] reported by reviewdog 🐶 [Canonical.016-No-inline-comments] Avoid inline comments in code blocks. Raw Output: {"message": "[Canonical.016-No-inline-comments] Avoid inline comments in code blocks.", "location": {"path": "docs/how-to/contribute.md", "range": {"start": {"line": 25, "column": 1}}}, "severity": "WARNING"}
unit-tests / Style checker: docs/how-to/contribute.md#L64
[vale] reported by reviewdog 🐶 [Canonical.004-Canonical-product-names] Use 'MicroK8s' instead of 'microk8s' Raw Output: {"message": "[Canonical.004-Canonical-product-names] Use 'MicroK8s' instead of 'microk8s'", "location": {"path": "docs/how-to/contribute.md", "range": {"start": {"line": 64, "column": 26}}}, "severity": "WARNING"}
unit-tests / Check license headers
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.

Artifacts

Produced during runtime
Name Size
report
769 Bytes