Improve weekly link checker reports and failure tracking

Aperta
  • Qualcosa non va?
#391 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
43/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, yaml
Ambito
ci-cd, devops

Direzione di ricerca

Start with .github/workflows/link-checker.yml and the linked weekly reports #365–#376 to understand how the workflow checks URLs and creates reports. Implement the report lifecycle and verification behavior described in the acceptance criteria, then validate unchanged, new, resolved, removed or excluded, blocked or rate-limited, and clean-run cases. Done means one open report tracks failure history, redirects are informational, and 403/429 checks are not silently treated as verified.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

The weekly link checker creates a new issue for each failing run and includes successful redirects alongside failures. Repeated failures make new problems harder to notice. The workflow also globally accepts HTTP 403 and 429 responses, which can hide inaccessible or unverified links.

The eight weekly reports from 6 September–25 October 2026 show why this matters:

URL Failed reports
cid.contact/routing/v1/providers/ (incomplete documentation example) 8/8
cha-ching.it (timeout) Latest 5
geoweb.network (TLS handshake failure) Latest 3
FilecoinWarmStorageService.sol source URL (404) First appears in #376

Reports: #365, #367, #368, #369, #372, #373, #374, #376.

Improve .github/workflows/link-checker.yml in three areas:

  1. Maintain one open report with failure history. Update the existing report instead of creating duplicate weekly issues. Show new, persistent, and resolved failures, with first-seen and last-checked information and the latest workflow-run link.
  2. Separate actionable failures from redirects. Put failures first and keep successful redirects in a collapsed informational section. Distinguish expected functional redirects (Google Forms submission endpoint, Cloudflare script, GitHub login) from ordinary webpage redirects worth updating.
  3. Review blanket acceptance of HTTP 403 and 429. Retry rate limits appropriately, respecting Retry-After where available, and surface checks that remain blocked or unverified. Any exceptions should have a documented, narrow URL scope and reason.

Acceptance criteria:

  • Consecutive runs with the same failures update the existing open report without creating another issue.
  • New and persistent failures are clearly distinguished, with first-seen and last-checked information.
  • Previously failing URLs are marked resolved only after successful verification; removals and exclusions are identified separately.
  • Successful redirects are informational and do not appear as broken links; the full report and workflow-run URL remain available.
  • HTTP 403/429 responses are not silently counted as verified working links; narrowly scoped exceptions are documented.
  • A clean run updates or closes the outstanding report.
  • Validate the report lifecycle with unchanged failures, a new failure, a successful recheck, a removed/excluded URL, blocked/rate-limited checks, and a clean run.

Individual link corrections and the incomplete CID-example exclusion are handled separately in draft PR #392.

Lingua principale
TypeScript
Stelle
4
Fork
10
Merge medio
4h 10m
PR unite (30g)
13

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di FilOzone/filecoin-cloud

Tutte le issue di FilOzone/filecoin-cloud

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.