Link Checker Report
Open
Nobody has claimed this yet.
automated issue
report
- Dominant language
- Python
- Stars
- 15.4k
- Forks
- 2.8k
- PR merge metrics
- No merged PRs in 30d
Description
Summary
| Status | Count |
|---|---|
| π Total | 676 |
| β Successful | 659 |
| β³ Timeouts | 2 |
| π Redirected | 0 |
| π» Excluded | 0 |
| β Unknown | 0 |
| π« Errors | 15 |
Errors per input
Errors in ./sections/07-DataSources.md
- https://www.data.gov/education/: Failed: Network error
- http://www.unicef.org/statistics/: Failed: Network error
- http://hls.harvard.edu/library/research/find-a-database/international-relations-human-rights-data/: Failed: Network error
- http://www.fitness.gov/resource-center/facts-and-statistics/: Failed: Network error
- http://www.broadinstitute.org/cgi-bin/cancer/datasets.cgi: Failed: Network error
- https://phpartners.org/health_stats.html: Timeout
- https://www.ncdc.noaa.gov/wdcmet/data-access-search-viewer-tools/world-weather-records-wwr-clearinghouse: Timeout
Errors in ./sections/03-AdvancedSkills.md
- https://bomb.codes/: Failed: Network error
- file:///home/runner/work/Cookbook/Cookbook/sections/missing: Failed: Cannot find file
- https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-common-terms-query.html: Failed: Network error
- https://github.com/gschmutz/stream-processing-workshop/tree/master/04-twitter-data-ingestion-with-streamsets: Failed: Network error
Errors in ./sections/06-BestPracticesCloud.md
- file:///home/runner/work/Cookbook/Cookbook/sections/sections/01-Introduction.md: Failed: Cannot find file
Errors in ./sections/05-CaseStudies.md
- https://www.datasciencecentral.com/profiles/blogs/20-data-science-systems-used-by-amazon-to-operate-its-business: Failed: Network error
Errors in ./sections/09-BooksAndCourses.md
- file:///home/runner/work/Cookbook/Cookbook/sections/BooksAndCourses: Failed: Cannot find file
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the reported links in sections/07-DataSources.md, sections/03-AdvancedSkills.md, sections/06-BestPracticesCloud.md, sections/05-CaseStudies.md, and sections/09-BooksAndCourses.md, using the linked GitHub Actions output for context. Check which URLs and local file references are invalid, then update the affected documentation and rerun the link checker until the reported errors are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100