conventional-changelog/standard-version

Commits are not grouped by type

Open

#149 opened on Nov 28, 2016

View on GitHub
 (3 comments) (4 reactions) (0 assignees)JavaScript (7,442 stars) (825 forks)batch import
enhancementhelp wanted

Description

Hello

I'm using the CLI version of standard-version, but I don't understand why the commits are not grouped by type when the changelog is generated.

For example the generated output looks like

### Features

* **auth:** add box id to token summary ([azerty](https://bitbucket.org/xxx))
* **auth:** add token request to a REST service ([azerty](https://bitbucket.org/xxx))

To generate my changelog I just use the basic executable

./node_modules/.bin/standard-version

Maybe I'm doing something wrong?

Thanks for your help.

Contributor guide

Tech stack
javascriptnodejs
Domain
clitoolingdeveloper experience
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Understanding of conventional commits formatBasic knowledge of standard version configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate whether the user's commit messages follow the conventional commits specification. The issue may be caused by mismatched commit types or missing configuration for grouping. Check the standard version documentation for options like ' types' and verify the user's commit log. The provided example shows commits grouped under 'Features', so the user may expect additional groups that are not present. Examine the repository's issue comments for further details.