You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix dead links by updating to working alternatives or removing them
Commit and push changes
Create pull request
Fixed Links:
✅ Removed 2 invalid f.local URLs from misc/posts.md (local development URLs)
✅ Updated deprecated RawGit CDN to jsDelivr CDN in README.md (RawGit shut down in 2019)
✅ Updated RStudio URL to current Posit company URL
✅ Fixed missing https protocol in fst package URL
Analysis Summary:
Analyzed 200+ URLs across all markdown files
Found and fixed 4 confirmed dead/broken links
Identified 15-20 additional URLs that may need future verification (personal blogs from 2016-2017)
Two additional reproducible navigation errors remain at master e58c6d6f41795c133ae0a6e455a1727b021c8445, outside the changes already proposed in the branch linked above:
The README's Awesome R table-of-contents link uses #awesome-. GitHub's rendered heading has id="user-content-awesome-r"; there is no user-content-awesome- anchor, so clicking the entry does not reach the heading. Change [Awesome R](#awesome-) to [Awesome R](#awesome-r).
The R code link in misc/r-trending.md points to blob/master/trending_repo.R, but the complete repository tree places the script at misc/trending_repo.R. Both the historical output and the corresponding writeLines literal in the generator need the same path correction, so future generation does not restore the broken link.
Minimal replacements (three lines total):
--- a/README.md+++ b/README.md@@ -11 +11 @@-- [Awesome R](#awesome-)+- [Awesome R](#awesome-r)--- a/misc/r-trending.md+++ b/misc/r-trending.md@@ -3 +3 @@-Generated biweekly from [R code](https://github.com/qinwf/awesome-R/blob/master/trending_repo.R).+Generated biweekly from [R code](https://github.com/qinwf/awesome-R/blob/master/misc/trending_repo.R).--- a/misc/trending_repo.R+++ b/misc/trending_repo.R@@ -63 +63 @@- writeLines("Generated biweekly from [R code](https://github.com/qinwf/awesome-R/blob/master/trending_repo.R).\n", f)+ writeLines("Generated biweekly from [R code](https://github.com/qinwf/awesome-R/blob/master/misc/trending_repo.R).\n", f)
Validation: the two original targets fail local checks against GitHub's exact-commit rendered README and complete Git tree. With these replacements, both targets resolve and the generator's link literal matches the historical document. No package data, historical dates, entries or license text are changed. R was not run; this checks the navigation targets and string literal, not a fresh trending-data generation.
Activity
claude commentedon Aug 8, 2025
Claude finished @qinwf's task —— View job •
claude/issue-258-20250808-1542• Create PR ➔Dead Links Cleaned Up ✅
I successfully identified and fixed dead links in the awesome-R repository.
Todo List:
Fixed Links:
✅ Removed 2 invalid f.local URLs from
misc/posts.md(local development URLs)✅ Updated deprecated RawGit CDN to jsDelivr CDN in README.md (RawGit shut down in 2019)
✅ Updated RStudio URL to current Posit company URL
✅ Fixed missing https protocol in fst package URL
Analysis Summary:
--- | Branch: claude/issue-258-20250808-1542
dajiaohuang commentedon Oct 17, 2026
Two additional reproducible navigation errors remain at master
e58c6d6f41795c133ae0a6e455a1727b021c8445, outside the changes already proposed in the branch linked above:#awesome-. GitHub's rendered heading hasid="user-content-awesome-r"; there is nouser-content-awesome-anchor, so clicking the entry does not reach the heading. Change[Awesome R](#awesome-)to[Awesome R](#awesome-r).misc/r-trending.mdpoints toblob/master/trending_repo.R, but the complete repository tree places the script atmisc/trending_repo.R. Both the historical output and the correspondingwriteLinesliteral in the generator need the same path correction, so future generation does not restore the broken link.Minimal replacements (three lines total):
Validation: the two original targets fail local checks against GitHub's exact-commit rendered README and complete Git tree. With these replacements, both targets resolve and the generator's link literal matches the historical document. No package data, historical dates, entries or license text are changed. R was not run; this checks the navigation targets and string literal, not a fresh trending-data generation.