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

What am I not understanding...

Open
#270 8 comments 5 reactions 0 assignees View on GitHub
bug
Dominant language
JavaScript
Stars
897
Forks
313
PR merge metrics
No merged PRs in 30d

Description

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???

Contributor guide

Open the contributing guide

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github, javascript
Domain
cli, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.