github-tools / github-tools/github-release-notes

Support pull requests without associated issues

Ouverte
#79 1 commentaire 7 réactions 0 personnes assignées Voir sur GitHub
enhancement
Langage dominant
JavaScript
Étoiles
897
Forks
313
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
github, javascript, node.js
Domaine
release
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.