github-starred/conventionalcommits.org
2
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2026-03-12 02:17:21 -05:00
Code Issues 153 Packages Projects Releases Wiki Activity

Release notes are the same with every release #152

New Issue
Closed
opened 2026-02-17 11:50:04 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-17 11:50:04 -06:00
Owner
Copy Link

Originally created by @raul1991 on GitHub (Jul 6, 2022).

I am using the following to generate complete release notes which is working as expected.

./node_modules/.bin/conventional-changelog --preset conventionalcommits --infile CHANGELOG.md --append --same-file --release-count 0

but when I don't give --release-count option, I expect it to give me release notes only for 1 release but it still outputs the entire thing.

I have tagged my release after generating the complete release notes.

Originally created by @raul1991 on GitHub (Jul 6, 2022). I am using the following to generate complete release notes which is working as expected. ``` ./node_modules/.bin/conventional-changelog --preset conventionalcommits --infile CHANGELOG.md --append --same-file --release-count 0 ``` but when I don't give --release-count option, I expect it to give me release notes only for 1 release but it still outputs the entire thing. I have tagged my release after generating the complete release notes.
GiteaMirror commented 2026-02-17 11:50:06 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Sep 7, 2022):

@raul1991 I think you opened the issue in the wrong repository :)
Closing, for now, let me know if you need help with the conventional commit specification

@damianopetrungaro commented on GitHub (Sep 7, 2022): @raul1991 I think you opened the issue in the wrong repository :) Closing, for now, let me know if you need help with the conventional commit specification
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
discussion
enhancement
greenkeeper
help wanted
meeting-agenda
operations
process
pull-request
Mirrored from GitHub Pull Request
 question
suggestion
support
triaged
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#152
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?