conventional-changelog/standard-version

Usage in monorepo nx workspace

Open

#445 创建于 2019年8月26日

在 GitHub 查看
 (13 评论) (43 反应) (0 负责人)JavaScript (7,442 star) (825 fork)batch import
help wantedquestion

描述

Hi, I am using nx workspace to handle multiple angular projects as well as shared libraries. Let' s assume a folder structure like this:

|_package.json
|_CHANGELOG.md
|_projectA
  |_package.json
  |__CHANGELOG.md
|_projectB
  |_package.json
  |_CHANGELOG.md

I am trying to figure out a way to use conventional-changelog in my release process. I want to have seperated changelogs for each project and one root changelog. By using conventional commits I would like to somehow define the scope of the commit (e.g. that this feat() only affects projectA and thus, is only mentioned in this specific changelog.

Is this possible or is this a wrong approach in a monorepo?

Help appreciated.

贡献者指南

技术栈
javascripttypescriptnodejs
领域
toolingreleasedeveloper experiencecli
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Nx workspace basicsconventional commitsstandard version CLI
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Examine the issue comments for potential workarounds and solutions. Explore standard version's tag prefix and skip flags to generate per project changelogs. Consider using Nx's built in changelog generation or a custom script. The repository's documentation may also provide guidance on monorepo setups.
Usage in monorepo nx workspace · conventional-changelog/standard-version#445 | Good First Issue