From c63e37d20add64c8eabfe59c4d903fbccd4b94f4 Mon Sep 17 00:00:00 2001 From: Daniel Farrell Date: Wed, 5 Oct 2022 16:45:36 -0400 Subject: [PATCH] Use inline HTML for heading tags, not Gitiles MD This syntax for creating ID tags for headings (typically with complex names) isn't supported in CommonMark, which is the standard used by our MD linter. It's valid syntax in Gitiles MD, which is why the links work. Upstream feature request to add support for this type of header ID: DavidAnson/markdownlint#570 This is required for submariner-io/submariner-website#827. Signed-off-by: Daniel Farrell --- src/content/development/release-process/_index.en.md | 2 +- src/content/development/shipyard/targets/_index.en.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/development/release-process/_index.en.md b/src/content/development/release-process/_index.en.md index c66b34cef..d733f6cbf 100644 --- a/src/content/development/release-process/_index.en.md +++ b/src/content/development/release-process/_index.en.md @@ -308,7 +308,7 @@ Once the `submariner-operator` and `submariner-charts` releases are complete, we unpin the Shipyard Dapper base image version, that is set it back to `devel`. For ongoing development we want each project to automatically pick up the latest changes to the base image. -### Step 5: Verify Release {id="verify"} +### Step 5: Verify Release You can follow any of the [quick start guides](../../getting-started/quickstart). diff --git a/src/content/development/shipyard/targets/_index.en.md b/src/content/development/shipyard/targets/_index.en.md index 72f2ca553..e86b9f154 100644 --- a/src/content/development/shipyard/targets/_index.en.md +++ b/src/content/development/shipyard/targets/_index.en.md @@ -58,7 +58,7 @@ make deploy * **`DEPLOYTOOL`**: The tool used to deploy Submariner itself (defaults to `operator`). * **`LIGHTHOUSE`**: Deploys Lighthouse in addition to the basic Submariner deployment (defaults to `false`). -### E2E (End to End) {#e2e} +### E2E (End to End) Runs end to end testing on the deployed environment (if one isn't created yet, this target will first invoke the `deploy` target to do so). The tests are taken from the project, unless it has no specific end to end tests, in which case generic testing using `subctl verify` is