Simplify docs URL to use consistent raw GitHub link#210
Merged
Conversation
Use the GitHub raw URL for both TTY and non-TTY output so the docs link can be fetched directly as Markdown by AI agents.
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
3 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.
Summary
Unified the documentation URL handling to always use the raw GitHub content link, removing the conditional logic that previously served different URLs based on whether the output was a TTY.
Key Changes
raw/refs/tagspathImplementation Details
The new URL format (
https://github.com/apify/mcpc/raw/refs/tags/v${mcpcVersion}/README.md) provides direct access to the raw Markdown file and works reliably across different contexts (AI agents, pipes, and human users), eliminating the need for environment-specific URL selection.https://claude.ai/code/session_01UrgrTcgdKAv1H2zXe4DYzk