Ignore bot-blocked links in myst link checker#49
Merged
Conversation
Add error_rules to myst.yml to suppress link-resolve failures for domains that return 403/429 to CI but are valid for human users, fixing the nightly build failure. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
|
👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below. |
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
1 participant
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.
Summary
myst build --stricttreats link-resolve failures as errorsjournals.ametsoc.org,noaa.gov,mrms.nssl.noaa.gov,github.com/ARM-Development) all work fine for human users but return 403/429 to CI botserror_rulestomyst.ymlto suppress these failures, using the same mechanism already in the upstreampythia-configTest plan
🤖 Generated with Claude Code