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

override wrong release note

未關閉
#303 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
JavaScript
星號
897
分支
313
PR 合併指標
30 天內沒有已合併 PR

描述

when i run "gren release":

(base) root@ubuntu:~# gren release '--username=haiming3' '--repo=mercuy' '--data-source=prs' '--tags=build.20210901..build.20210825' '--token=' --override

🤖 - Generate release notes:
===================================
✔ Releases found: 3
✔ Tags found: build.20210825, build.20210901
✔ Pull Requests found: 86
✔ build.20210825 has been successfully updated!
See the results here: https://github.com/haiming3/mercuy/releases/tag/build.20210825

question:
As seen above, gren will update my "build. 20210825". Shouldn't it update my "build. 20210901"?

My configuration is -- tags = build. 20210901.. build. 20210825 '

build. 20210901 is my new tag

貢獻指南

開啟貢獻指南

研究方向

Reproduce the reported `gren release` command using `--override` and the tag range `build.20210901..build.20210825`. Start by tracing how the release command interprets the `--tags` range and selects the release to update. Done means the command updates the intended newer tag, with coverage for this tag-order case.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
javascript, node.js
領域
cli, release
Issue 類型
缺陷
難度
3/5
預估耗時
1-2 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。