conventional-changelog/standard-version

Commits are not grouped by type

Open

#149 创建于 2016年11月28日

在 GitHub 查看
 (3 评论) (4 反应) (0 负责人)JavaScript (7,442 star) (825 fork)batch import
enhancementhelp wanted

描述

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.

贡献者指南

技术栈
javascriptnodejs
领域
clitoolingdeveloper experience
议题类型
research
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Understanding of conventional commits formatBasic knowledge of standard version configuration
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
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.
Commits are not grouped by type · conventional-changelog/standard-version#149 | Good First Issue