Repository navigation
docs: fix 15 broken relative links across four READMEs - #79
Open
bcfmtolgahan wants to merge 1 commit into
Open
bcfmtolgahan wants to merge 1 commit into
bcfmtolgahan wants to merge 1 commit into
Conversation
Three unrelated path errors leave 15 markdown links pointing at files that do not exist. On GitHub and on any case-sensitive filesystem these render as 404s, cutting readers off from the reference documents the skills load at runtime. - aws-managed-definitions/README.md: the two portfolio readiness links omit the "-analysis" suffix the actual files carry. - community-sourced-transformations/jboss-to-springboot/README.md: 12 links use "References/" while the tracked directory is "references/". These resolve on case-insensitive filesystems (macOS, Windows) but 404 on GitHub and Linux. - community-sourced-transformations/kubernetes-readiness-migration/README.md: links java-maven-patterns.md, which was renamed to java-jvm-patterns.md. SKILL.md already uses the new name, so only the README lagged. The directory trees in the same files are updated to match. Verified by walking every tracked .md file and resolving each relative link against "git ls-files" (case-sensitive, so the macOS filesystem cannot mask the References/ mismatch). Before: 16 broken links. After: 1, scaled-execution-containers/README.md -> docs/PUBLIC_ECR.md, left untouched because that file was never committed and needs content rather than a path correction.
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.
Issue #, if available: n/a
Description
Three unrelated path errors leave 15 markdown links pointing at files that do not exist. On GitHub and on any case-sensitive filesystem these render as 404s, which cuts readers off from the reference documents the skills load at runtime.
aws-managed-definitions/README.md-analysissuffix the actual files carry (portfolio-modernization-readiness.mdvsportfolio-modernization-readiness-analysis.md).community-sourced-transformations/jboss-to-springboot/README.mdReferences/while the tracked directory isreferences/. These resolve on case-insensitive filesystems (macOS, Windows) but 404 on GitHub and on Linux.community-sourced-transformations/kubernetes-readiness-migration/README.mdjava-maven-patterns.md, which was renamed tojava-jvm-patterns.md.SKILL.mdalready uses the new name, so only the README lagged behind.The directory trees in the same files are updated to match. No other content was touched.
Testing
Walked every tracked
.mdfile, extracted each relative markdown link (after stripping fenced and inline code), and resolved it againstgit ls-files— case-sensitively, so the macOS filesystem cannot mask theReferences/mismatch.The one remaining is
scaled-execution-containers/README.md->docs/PUBLIC_ECR.md. I left it alone deliberately: that file was never committed, so it needs content rather than a path correction. Happy to open a separate issue for it if useful.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.