Fix broken internal links: strip absolute local paths from all Markdown files#95
Draft
Fix broken internal links: strip absolute local paths from all Markdown files#95
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…aths Agent-Logs-Url: https://github.com/TrustSignal-dev/TrustSignal/sessions/4ec05d32-8834-4515-a35e-842fc71ba9fe Co-authored-by: chrismaz11 <24700273+chrismaz11@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix broken README links by replacing absolute paths
Fix broken internal links: strip absolute local paths from all Markdown files
Apr 1, 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.
Summary
/Users/christopher/Projects/trustsignal/...), making every internal link broken on GitHub. Stripped the prefix from all affected files so links resolve as proper relative paths.Files changed:
README.md,bench/README.md,wiki/Home.md,wiki/What-is-TrustSignal.md,wiki/Quick-Verification-Example.md,wiki/API-Overview.mdPattern fixed (42 occurrences):
AI Disclosure (optional)
Review Checklist
Original prompt
Fix broken README links: replace absolute local paths with relative paths
All internal links in the repository's Markdown files use absolute local filesystem paths (
/Users/christopher/Projects/trustsignal/...) instead of relative repository paths. This causes every internal link to be broken when viewed on GitHub.What needs to change
Across all Markdown files in the repository, find and replace every occurrence of the absolute path prefix
/Users/christopher/Projects/trustsignal/with an empty string so the links become proper relative paths.Known affected files
README.md— at least these lines have broken links:(/Users/christopher/Projects/trustsignal/docs/verification-lifecycle.md)→(docs/verification-lifecycle.md)(/Users/christopher/Projects/trustsignal/demo/README.md)→(demo/README.md)bench/README.md— lines 34–35, 43:(/Users/christopher/Projects/trustsignal/bench/results/latest.json)→(bench/results/latest.json)(/Users/christopher/Projects/trustsignal/bench/results/latest.md)→(bench/results/latest.md)(/Users/christopher/Projects/trustsignal/bench/fixtures)→(bench/fixtures)Other Markdown files — search the entire repository for any other
.mdfiles containing/Users/christopher/Projects/trustsignal/and fix those as well.How to fix
In every affected file, replace the prefix
/Users/christopher/Projects/trustsignal/with nothing, so that:becomes:
Make sure no other content is changed — only the link targets should be updated.
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: why does the readme page look messed up'
Assistant:
Let me take a look at the README file in the repository to understand what might be causing display issues.
Assistant: I found the problem! Your README (and
bench/README.md) is full of absolute local file paths instead of relative repository paths. All the links point to/Users/christopher/Projects/trustsignal/...— which is a path on your local machine. On GitHub, these links are completely broken (they resolve to nothing), making the page look "messed up" with dozens of dead links.Here's what's happening — nearly every internal link uses this pattern:
When it should be a relative path like:
Affected links in
README.md(lines with the issue):/Users/christopher/Projects/trustsignal/docs/verification-lifecycle.mddocs/verification-lifecycle.md/Users/christopher/Projects/trustsignal/demo/README.mddemo/README.md/Users/christopher/Projects/trustsignal/docs/partner-eval/quickstart.mddocs/partner-eval/quickstart.md/Users/christopher/Projects/trustsignal/docs/partner-eval/api-playground.mddocs/partner-eval/api-playground.md/Users/christopher/Projects/trustsignal/openapi.yamlopenapi.yaml/Users/christopher/Projects/trustsignal/postman/TrustSignal.postman_collection.jsonpostman/TrustSignal.postman_collection.json/Users/christopher/Projects/trustsignal/postman/TrustSignal.local.postman_environment.jsonpostman/TrustSignal.local.postman_environment.jsonThe same issue also exists in
bench/README.md(lines 34–35, 43).How to fix it
Would you like me to open a PR that replaces all the absolute local paths (
/Users/christopher/Projects/trustsignal/...) with proper relative paths across the affected README files? This is a straightforward find-and-replace — strip the/Users/christopher/Projects/trustsignal/prefix from every link so they work correctly on GitHub.User: yes
Assistant: I've kicked off a Copilot coding agent to create a PR that replaces all the broken absolute local paths (
/Users/christopher/Projects/trustsignal/...) with proper relative paths across the affected Markdown files.You'll receive a notification on GitHub once the pull request is ready for review. The fix is straightforward — it just strips the
/Users/christopher/Projects/trustsignal/prefix from every link target so they resolve correctly on GitHub.This pull request was created from Copilot chat.