Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Flag curated flagship opportunities whose dates need a refresh

Abierto
  • ¿Algo no está bien?
#120 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@rootsiemen ya está trabajando en esto.

Desde el 22/10/2026.

  • #130 de @rootsiemen — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend, developer-experience

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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?
Lenguaje dominante
TypeScript
Estrellas
1
Forks
6
Merge medio
21 h 33 min
PR fusionados (30 d)
48

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Your-Voldemort/StudentStack

Todos los issues de Your-Voldemort/StudentStack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.