conventional-changelog/standard-version

Usage in monorepo nx workspace

オープン

#445 opened on 2019/08/26

 (13 件のコメント) (43 件のリアクション) (0 人の担当者)JavaScript (825 件のフォーク)batch import
help wantedquestion

Repository metrics

Stars
 (7,442 個のスター)
PR merge metrics
 (30d に merged PR はありません)

説明

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.

コントリビューターガイド