improve lychee config (again), fix links in customize section#470
Merged
improve lychee config (again), fix links in customize section#470
Conversation
Contributor
Author
…pecific domain exclusions, plus better caching
42e6da1 to
9bc189e
Compare
avanscoy
reviewed
Jan 14, 2026
avanscoy
reviewed
Jan 14, 2026
avanscoy
approved these changes
Jan 14, 2026
daniloasis-auth0
pushed a commit
to daniloasis-auth0/docs-v2
that referenced
this pull request
Jan 23, 2026
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
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.
description
this PR tweaks the newly-improved lychee config:
and then i fixed all the links in the
/customizesection of the docs. 🙂testing
one test is the results of lychee on this PR! unfortunately the salesforce links sometimes redirect with language locale and then sometimes also redirect back ... not sure what to do about that.
you can also test by running lychee locally against the customize section. from the root of the repo:
you'll probably see a few 503s from
core.telegram.orgbecause okta blocks the domain (but the URLs do work). you'll also see a 404 for theauth0-awsgithub repo, but there's no replacement link because the repo was deleted. i erred on the side of not deprecating a half dozen content articles in this PR to avoid scope creep, but we probably should.