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

Enhancement: Link-health cron admin notification (email/slack)

Abierto
  • ¿Algo no está bien?
#41 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend-api-design

Línea de trabajo

Start with issue #38, since this work depends on Phase 5 email infrastructure, then read src/app/api/cron/link-health/route.ts and src/lib/link-health.ts to understand the existing weekly check and summary. The issue leaves email versus Slack/webhook open and also calls for an admin preference; clarify those choices before starting. Done means newly broken links trigger the agreed notification with the requested details and admins can opt in or out.

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

Descripción

enhancement

Description

PRD §8.6 requires: "4xx/5xx or timeout → status = 'broken', admin gets a summary notification"

Currently (PROGRESS.md judgment call #3): "Link-health 'admin gets a summary notification' (§8.6) is the dashboard's status-count line, not an email. No email provider is wired up yet (that's Phase 5's digest email, §8.12); building one just for this would be scope creep."

Now that we're planning Phase 5 email infrastructure, this should be implemented properly.

Current State

  • src/app/api/cron/link-health/route.ts runs weekly, updates status, logs summary to console
  • Admin dashboard shows counts and max(last_verified_at)
  • No proactive notification when links break

Expected Behavior

When link-health cron finds broken links:

  • Send email to admin (using Resend/Mailvex from Phase 5)
  • Or send Slack/webhook notification
  • Include: list of newly broken links, total checked, summary stats

Implementation Plan

  1. Wait for Phase 5 email infrastructure (issue #38)
  2. Modify link-health cron to send notification:
    • After processing, if broken > 0, send email
    • Template: "StudentStack Link Health: X broken links found"
    • List each broken resource with name, URL, category
  3. Add notification preference: Admin can opt in/out

Files to Modify

  • src/app/api/cron/link-health/route.ts - add notification call
  • src/lib/email.ts (from Phase 5) - add link-health notification template
  • src/lib/link-health.ts - return detailed broken link info

Email Template

Subject: StudentStack Link Health Alert — 5 broken links detected

The weekly link health check found 5 newly broken links out of 551 checked.

Broken Resources:
1. GitHub Copilot — https://education.github.com/pack — Development Tools
2. AWS Free Tier — https://aws.amazon.com/education/awseducate/ — Cloud & Hosting
...

View in admin dashboard: https://your-domain.com/admin

— StudentStack Bot

Alternative: Slack/Webhook

  • Simpler than email for now
  • Add SLACK_WEBHOOK_URL env var
  • Post to #alerts channel
Lenguaje dominante
TypeScript
Estrellas
1
Forks
6
Merge medio
11 h 16 min
PR fusionados (30 d)
16

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.