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

Review feed requests in the operations API

Abierto
  • ¿Algo no está bien?
#1,866 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python, yaml
Área
api, backend

Línea de trabajo

Start with the endpoint definitions in OperationsAPI.yaml, then find the existing create-feed and update-feed logic that approval should reuse. Done means the list, get, approve and reject endpoints exist and work, approving an add request links the new feed to the request, approving an update applies changes to the linked feed, and only pending requests can be reviewed. The issue depends on an unresolved decision about how approved feeds reach each environment and who assigns stable IDs, so confirm that first.

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

Descripción

Describe the problem

Add and update feed requests (#1864, #1865) are stored as pending and do not change any feed. There is no way to review them and apply the approved ones.

Proposed solution

Add operations API endpoints to review feed requests.

  • List feed requests, filtered by type, status and feed ID, and get a single request.
  • Approve a request:
    • add: create the GTFS or GTFS-RT feed using the existing create feed logic, and set the request's feed ID.
    • update: apply the changes to the linked feed using the existing update feed logic.
  • Reject a request with a reason.
  • Set the request status to approved or rejected and record who reviewed it and when. Keep the record so the feed's request history is preserved.
  • Allow the reviewer to edit the request payload before approving.
  • Close GitHub related issue with comment.

Acceptance criteria

  • Endpoints are defined in OperationsAPI.yaml and implemented.
  • Approving an add request creates the feed and links it to the request.
  • Approving an update request applies the changes to the linked feed.
  • Only pending requests can be approved or rejected.

Out of scope

  • Admin web UI for reviewing requests (mobilitydata-operations-web).
  • Notifying the submitter and closing the GitHub issue.
Alternatives you've considered

Reviewers copy the request data into the existing create/update feed endpoints by hand. That keeps the manual step and doesn't link the feed to its request.

Additional context

Depends on the decision on how approved feeds reach every environment and who assigns stable IDs. If approval opens a PR on the catalogs repo instead of writing to the database directly, the approve step changes accordingly.

Lenguaje dominante
Python
Estrellas
34
Forks
7
Merge medio
2 d 4 h
PR fusionados (30 d)
8

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 MobilityData/mobility-feed-api

Todos los issues de MobilityData/mobility-feed-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.