github-tools / github-tools/github-release-notes
Support pull requests without associated issues
- 主要言語
- JavaScript
- スター
- 897
- フォーク
- 313
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
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.
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- github, javascript, node.js
- 領域
- release
- issue の種類
- 機能追加
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100