Link Checker Report

Open
#567 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
documentation

Research direction

Start with the link-checker report and trace the listed errors in build/_sources/guides/calendar.rst.txt, guides/meetup.rst.txt, guides/promotion.rst.txt, and the operations files back to their source documents. Rerun the link checker after reviewing the reported Slack and other redirects; done means the unintended errors are resolved or explicitly handled and the report is clean.

Written by the indexing model from the issue text.

Description

broken links

Summary

Status Count
πŸ” Total 3176
πŸ”— Unique 870
βœ… Successful 2893
⏳ Timeouts 0
πŸ”€ Redirected 65
πŸ‘» Excluded 242
❓ Unknown 0
🚫 Errors 41
β›” Unsupported 0

Errors per input

Errors in build/_sources/guides/calendar.rst.txt
Errors in build/_sources/guides/meetup.rst.txt
Errors in build/_sources/guides/promotion.rst.txt
Errors in build/_sources/operations/domains.rst.txt
Errors in build/_sources/operations/meeting-notes/2022-2025.md.txt
Errors in build/_sources/operations/support.rst.txt
Errors in build/guides/calendar.html
Errors in build/guides/meetup.html
Errors in build/guides/promotion.html
Errors in build/operations/bylaws.html
Errors in build/operations/elections.html
Errors in build/operations/meeting-notes/2019-2022.html
Errors in build/operations/meeting-notes/2022-2025.html
Errors in build/operations/runbooks.html
Errors in build/operations/support-money.html
Errors in build/operations/support.html

Redirects per input

Redirects in build/_sources/guides/calendar.rst.txt
Redirects in build/_sources/guides/meetup.rst.txt
Redirects in build/_sources/guides/promotion.rst.txt
Redirects in build/_sources/guides/pyladies-runs.rst.txt
Redirects in build/_sources/operations/domains.rst.txt
Redirects in build/contributing.html
Redirects in build/guides/calendar.html
Redirects in build/guides/meetup.html
Redirects in build/guides/promotion.html
Redirects in build/guides/pyladies-runs.html
Redirects in build/index.html
Redirects in build/operations/bylaws.html
Redirects in build/operations/domains.html
Redirects in build/operations/elections.html
Redirects in build/operations/grants.html
Redirects in build/operations/meeting-notes/2019-2022.html
Redirects in build/operations/meeting-notes/2022-2025.html
Redirects in build/operations/runbooks.html
Redirects in build/operations/support-money.html
Redirects in build/operations/support.html
Redirects in build/operations/twitter.html
Redirects in build/operations/web-apps.html
Redirects in build/search.html

Full Github Actions output

Dominant language
Python
Stars
13
Forks
18
Avg merge
2h 42m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up β€” it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pyvec/docs.pyvec.org

All issues in pyvec/docs.pyvec.org

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.