Chore: Automate dead-link checking using GitHub Actions

[basantnema31]

Description

As a hub of resources, external links naturally rot and 404 over time. Having broken resources degrades the repository's credibility and frustrates users.

Proposed Solution

I propose implementing a GitHub Action (using lychee or awesome_bot) that runs on a weekly cron schedule. It will automatically crawl all markdown files in the repository, detect dead HTTP links, and automatically open a tracking issue for maintainers.

I would love to work on this automated CI chore under the GSSoC '24 program! Could you please assign it to me?

[github-actions]

Thank you for raising this issue! We'll look into it as soon as possible. Please ensure that the issue is not duplicate, and you read CONTRIBUUTING.md carefully. Your contributions are highly appreciated! 😊

[aayushprsingh]

Hi, I am a GSSoC 2026 contributor and would like to work on this. I have experience with HTML and can get started right away.

Here's how I'm thinking of approaching this:
I'll set up a lychee-action workflow scheduled via a weekly cron to scan all markdown and HTML files for 404s. I can configure it to automatically open a tracking issue with the full failure report whenever it detects a broken link, ensuring maintainers can triage and fix rot without manual auditing.

[PranavAgarkar07]

Hi! I'd like to work on this issue under GSSoC 2026.

Approach: I'll set up a GitHub Actions workflow using lycheeverse/lychee-action configured to run on a weekly cron schedule and on pushes to main. The action will crawl all markdown files, detect broken HTTP links, and auto-file a tracking issue with the broken URLs listed for maintainers. I'll fine-tune the exclude patterns to avoid false positives from common false-positive domains.

I have experience setting up CI workflows with GitHub Actions and maintaining link-checking pipelines in open-source projects. Please assign me this issue.