Repository navigation
Conversation
The v0.1.0 review (#2) flagged `proxy.alcf.anl.gov:3128` and `rest.kegg.jp/list/organism` as broken links. Both were already backticked code rather than links -- an HTTP proxy endpoint and a REST endpoint -- so neither was link rot, and both correctly fail a browser GET. But a reader hitting them has nothing to follow, and a link scanner has nothing to resolve. Each now cites a page that does resolve, beside the literal value: the ALCF getting-started docs for the proxy, and the KEGG REST API reference for the endpoint. The values themselves stay, because they are configuration a reader needs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
20 of 31 tasks
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.
Closes the last two link items from the v0.1.0 review (#2).
Both
proxy.alcf.anl.gov:3128andrest.kegg.jp/list/organismwere already backticked code rather than links — an HTTP proxy endpoint and a REST endpoint — so neither was link rot, and both correctly fail a browser GET. But a reader hitting them had nothing to follow, and a link scanner nothing to resolve.Each now cites a page that does resolve, beside the literal value: the ALCF getting-started docs for the proxy, and the KEGG REST API reference for the endpoint. Both return 200. The literal values stay — they are configuration a reader needs.
Type of Change
Compatibility
How Has This Been Tested?
ruffclean;tools/ci/check_doc_links.pyresolves all relative links. Docs-only change.New Dependencies, Data, or Assets
None.
AI/LLM Assistance
🤖 Generated with Claude Code