Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

fix(links): make the online link check green (23 errors since 2026-10-11)

Open Beginner friendly
#8,730 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, shell
Domain
ci-cd, tooling

Research direction

Start with the latest run linked in the issue and inspect the 23 reported URLs, then locate each URL in the repository and check its context. Fix links that have moved; for intentional placeholders or hosts that block bots, add an exact URL to .lycheeignore with a one-line reason. Dispatch maintenance-check-links-online.yml and confirm the run passes or fails only on man7.org.

Written by the indexing model from the issue text.

Description

priority: medium

Every run of maintenance-check-links-online.yml since 2026-10-11 has failed (10 of 10). The latest, https://github.com/melodic-software/claude-code-plugins/actions/runs/39417117475, reports 23 errors:

  • missing fragments on vendor docs pages
  • placeholder URLs in eval prompts
  • a 403 from udemy
  • a 404 on a GitHub issue

This blocks melodic-software/ci-workflows#739. Its acceptance criteria require a dispatched run of the shared online check that is green, or that fails only on man7.org.

Fix

Fix each broken link. Where a URL cannot be fixed (an intentional placeholder, or a host that blocks bots), add an exact-URL .lycheeignore entry with a one-line reason. Do not use broad patterns.

Verification

A workflow_dispatch run of the online link check passes.

Refs: melodic-software/ci-workflows#739

🤖 Generated with Claude Code

Dominant language
Shell
Stars
22
Forks
2
Avg merge
7h 57m
Merged PRs (30d)
938

Getting set up

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 melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.