-
Notifications
You must be signed in to change notification settings - Fork 66
Replaced the incorrect link in FAQ section of pyOpenMS documentation #469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughThis pull request updates the hyperlink in the FAQ section of the user guide. The change replaces an internal anchor link with a direct external URL pointing to a specific release version of the pyOpenMS documentation. There are no changes to any exported or public entities. Changes
Assessment against linked issues
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
This doesn't look right. But definitely NOT a link to another version of the docs! |
@jpfeuffer I've updated the link to use the correct internal reference as per the documentation structure. It now properly points to the relevant section in wrapping_workflows_new_classes.rst, and I've verified that it works correctly in the generated HTML. Let me know if any further changes are needed. Thanks for the feedback! |
Fixes #468
This PR fixes a broken link in the FAQ section of the PyOpenMS documentation. The previous link was incorrect, leading to a 404 error. The updated link now correctly points to the relevant resource.
Summary by CodeRabbit