github-tools / github-tools/github-release-notes
Consider switching to GraphQL
Abierto
internal
- Lenguaje dominante
- JavaScript
- Estrellas
- 897
- Forks
- 313
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
It makes sense to `gren` to use GitHub GraphQL as it would be much easier to manage and query what we need without different endpoints.
This could also potentially allow #79
---
Also coming from #134
Guía de contribución
Línea de trabajo
Start by tracing gren's current GitHub endpoint usage and reviewing issues #79 and #134 for context. Define the required GraphQL queries and migration scope; done means the project has an agreed implementation plan or a completed switch with release-note behavior preserved.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- graphql, javascript
- Área
- api, release
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 20/100