github-tools / github-tools/github-release-notes
What am I not understanding...
- Vorherrschende Sprache
- JavaScript
- Sterne
- 897
- Forks
- 313
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Please tell me why I'm not getting my second release and what from the docs am I missing??
```none
git tag 1.0
git push origin --tags
gren release
```
✔ 1.0 has been successfully created!
Now I make some change in the repo, commit & push..
```none
git tag 1.1
git push origin --tags
gren release
Getting gren config from local file /home/brett/repos/my-org/terraform-google-billing-budget/.grenrc
🤖 - Generate release notes:
===================================
✔ Releases found: 1
✔ Tags found: 1.0, 1.1
✔ Issues found: 5
Skipping 1.0 (use --override to replace it)
```
I would expect this to create the 1.1 release for me???
Beitragsleitfaden
Rechercherichtung
Start by reproducing the tag and gren release commands with the shown local .grenrc and compare the handling of tags 1.0 and 1.1. Done means gren creates the expected 1.1 GitHub release instead of skipping it.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- git, github, javascript
- Bereich
- cli, release
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 30/100