github-tools / github-tools/github-release-notes
Support pull requests without associated issues
- Lenguaje dominante
- JavaScript
- Estrellas
- 897
- Forks
- 313
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Pull requests have all the discussion, tagging, search, project management, and other features of issues. But often, in a `gren`-enabled project, I'm still forced to create a separate issue when I've already made the PR that would close it (e.g. for a previously-unreported problem) because otherwise, the release notes would be incomplete. This adds overhead to what can be a seamless GitHub workflow.
The solution: I think `gren` should treat merged PRs as their own, self-closing issues if they don't explicitly close any other issue.
Guía de contribución
Línea de trabajo
Start by tracing the release-note generation flow described for this Node module, especially how it gathers issues or commits from a tag and handles merged pull requests. Done means a merged PR that does not explicitly close another issue can appear as its own self-closing release-note entry without requiring a separate issue.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github, javascript, node.js
- Área
- release
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100