Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Flag curated flagship opportunities whose dates need a refresh

Aperta
#120 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@rootsiemen ci sta già lavorando.

Dal 22/10/2026.

  • #130 di @rootsiemen — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript

Direzione di ricerca

Start by reading src/lib/flagship-opportunities.ts and the existing weekly link-health webhook and admin dashboard entry points. The proposed scope and several behavior choices are explicitly open for maintainer discussion, including the six-month threshold and webhook behavior. Done means agreed refresh rules and destinations are implemented, with the CONTRIBUTING.md workflow note.

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

Descrizione

Problem

src/lib/flagship-opportunities.ts (#112) holds hand-verified dates for about 60 scholarships, fellowships, and programs. They go stale every cycle: once a deadline passes, the program shows as a past cycle until someone updates the file, and nothing tells the maintainer which entries need a refresh.

Proposed scope (for discussion before a PR)

  • A pure check that lists curated entries needing attention, each with a reason:
    • the deadline has passed (the next cycle is expected around its recurrence month)
    • there's no date yet and the program's usual month has arrived
    • verifiedOn is older than about 6 months
  • Mentorship programs, which have no deadlines, are never flagged.
  • A compact "Curated programs to re-check" section on the admin dashboard, linking to each entry's official source page.
  • A short summary added to the existing weekly link-health webhook message (opt-in, as today).
  • A note in CONTRIBUTING.md on the refresh workflow.

No schema change. The curated data itself isn't changed.

Questions for the maintainer

  1. Is the admin dashboard plus the existing webhook the right place, or would you prefer something else, such as a GitHub issue opened automatically?
  2. Is 6 months a sensible re-verify age?
  3. Should the weekly webhook fire when only stale entries exist and there are no broken links?
Lingua principale
TypeScript
Stelle
1
Fork
6
Merge medio
21h 33m
PR unite (30g)
48

Preparare l'ambiente

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 Your-Voldemort/StudentStack

Tutte le issue di Your-Voldemort/StudentStack

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.