github-tools / github-tools/github-release-notes
override wrong release note
- Vorherrschende Sprache
- JavaScript
- Sterne
- 897
- Forks
- 313
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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
Beitragsleitfaden
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- javascript, node.js
- Bereich
- cli, release
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100