Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

links: the weekly report lists the same ~27 bot-blocked hosts every week; add a per-entry hint and check licence URLs too

Offen
  • Stimmt etwas nicht?
#89 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
javascript, node.js
Bereich
backend, testing-qa

Rechercherichtung

Start with site/check-links.mjs for fetching and weekly report rendering, site/lib/link-check.mjs for status handling, and checks.mjs plus checks.test.mjs for Evidence URL parsing and validation. Read the current link-check flow and its tests first. Done means known blocked hosts can be recorded as checked by hand, retry and Evidence URL checks are reported, and tests cover the new field or allowlist.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement hardening priority: medium

Why it matters
Issue #77 (regenerated every Monday) carries a collapsed "Refused the checker (27)" list: Fab, BlenderKit, CloudCompare and other hosts return 403 to a plain fetch no matter how healthy the source is. The maintainer has to open each by hand every week, and nothing records that a host was already checked in a browser. Meanwhile the checker only fetches the entry's url; the licence page an Evidence line points to is never fetched, although that page disappearing is exactly the event the catalog exists to catch.

Evidence

  • site/check-links.mjs:56-63 sends one fetch with a generic UA and no retry; site/lib/link-check.mjs:29 maps 401/403/429 straight to blocked.
  • site/check-links.mjs:159 renders the recurring "Refused the checker" section.
  • #77 body: 27 blocked, 0 dead, 0 moved, 3 maintenance mismatches, so nearly all weekly noise is the blocked list.
  • docs/review-ledger.md (2026-10-13): "Fab listings in a browser (plain fetches return 403)".

Suggested approach

  1. Add an optional frontmatter field such as link_check: manual (with a short reason) that the validator accepts and the checker uses to list the entry under "checked by hand on " instead of "Refused". A host allowlist in site/config.json would also work and needs no per-entry edits.
  2. On 403/429, retry once with browser-like User-Agent, Accept-Language and Sec-Fetch-* headers.
  3. Also fetch any https:// URL in ## Evidence lines (already parsed by checks.mjs for dates) and report a dead licence page as its own section.
  4. Only include the blocked list when it changed since the previous run.

Done when
The weekly issue shows no recurring "Refused" rows for known hosts, a dead licence URL is reported, and checks.test.mjs covers the new field or allowlist.

Vorherrschende Sprache
JavaScript
Sterne
58
Forks
15
Ø Merge
16 Std. 53 Min.
Gemergte PRs (30 T.)
14

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TMHSDigital/Free-Game-Dev-Assets

Alle Issues in TMHSDigital/Free-Game-Dev-Assets

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.