Skip to content

Commit 0848a73

Browse files
author
Kingdon Barrett
committed
This commit should fail
Add a bad link id anchor that doesn't go anywhere (but isn't a 404) Signed-off-by: Kingdon Barrett <[email protected]>
1 parent 027b3b1 commit 0848a73

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/flux/flux-e2e.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Note that this guide has not been updated since more than a year ago. It does no
1111
Expect this doc to receive an overhaul soon.
1212
{{% /alert %}}
1313

14-
Below we describe the flow of data through Flux, from End to End.
14+
Below we describe the flow of data through Flux, from End to End. [Here is a link that doesn't go anywhere][#id-anchor-failure]
1515

1616
We assume a standard Flux installation, with all optional features enabled, then explain how Flux users can expect their change to flow through the stages
1717
of its life as a commit, and describe how the commit data passes through the Flux system and the cluster, in rough chronological order. We tried to cover

0 commit comments

Comments
 (0)