Lint (Docs) #83245
Annotations
3 warnings
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Run the linter:
docs/pages/admin-guides/management/operations/breakglass-access.mdx#L8
[vale] reported by reviewdog 🐶
[messaging.capitalization] Capitalize the names of Teleport services and features (Teleport agent is incorrect). See the Core Concepts page (https://goteleport.com/docs/core-concepts/) for a reference.
Raw Output:
{"message": "[messaging.capitalization] Capitalize the names of Teleport services and features (Teleport agent is incorrect). See the Core Concepts page (https://goteleport.com/docs/core-concepts/) for a reference.", "location": {"path": "docs/pages/admin-guides/management/operations/breakglass-access.mdx", "range": {"start": {"line": 8, "column": 8}}}, "severity": "WARNING"}
|
Run the linter:
docs/pages/admin-guides/management/operations/breakglass-access.mdx#L10
[vale] reported by reviewdog 🐶
[structure.architecture-h2] In a how-to guide, the first H2-level section must be called `## How it works`. Use this section to include 1-3 paragraphs that describe the high-level architecture of the setup shown in the guide, i.e., which infrastructure components are involved and how they communicate. If there is already architectural information in the guide, include it in a `## How it works` section.
Raw Output:
{"message": "[structure.architecture-h2] In a how-to guide, the first H2-level section must be called `## How it works`. Use this section to include 1-3 paragraphs that describe the high-level architecture of the setup shown in the guide, i.e., which infrastructure components are involved and how they communicate. If there is already architectural information in the guide, include it in a `## How it works` section.", "location": {"path": "docs/pages/admin-guides/management/operations/breakglass-access.mdx", "range": {"start": {"line": 10, "column": 1}}}, "severity": "WARNING"}
|
Loading