fix(docs): repair broken absolute links to moved doc pages - #1166
Merged
Merged
Conversation
blotus
approved these changes
Sep 16, 2026
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes 14 absolute
doc(s).crowdsec.netURLs (44 occurrences, current + versioned docs) that 404 after page moves, e.g./docs/next/parsers/intro→/docs/next/log_processor/parsers/intro/.Every new target returns 200 live, and the 3 anchors (
#testing-waf-component,#labels,#raw-metrics) exist on their pages.Absolute URLs skip the build's broken-link check; with #1165, all 52 in the docs now resolve.