conventional-changelog/standard-version

Usage in monorepo nx workspace

Open

#445 opened on 2019年8月26日

GitHub で見る
 (13 comments) (43 reactions) (0 assignees)JavaScript (7,442 stars) (825 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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