You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I am looking for a way to manage release notes for a multi-package repository, that is, a repository containing multiple packages or subprojects. For example, consider a web application repository holding different sub packages like frontend, backend and client:
webapp_repo/
├── backend
├── client
└── frontend
Each subpackage has its own versioning and its version may change independently of other packages. For this reason, I need a way to have separate release notes for each package.
The current implementation of gitchangelog does not seem to provide a way to solve the problem. Instead, it produces a list of all commits of the repo in chronological order regardless the subpackage each commit comes from.
So, I think having a --path command line would allow to produce a separate changelog for each subpackage. I imagine something like this:
Also it would be nice if the tool would also look for a .gitchangelog.rc within the provided path. This would allow each subpackage to have its own configuration.
I found a similiar PR #112 which suggests to hard code the path as a config variable in the gitchangelog.rc. However, I think having a --path command line argument would be much more flexible as it would allow to set the path in runtime depending on the subdirectory. This would allow to build the Release Notes for a specific package whenever there is a release for that package
The text was updated successfully, but these errors were encountered:
Hello,
I am looking for a way to manage release notes for a multi-package repository, that is, a repository containing multiple packages or subprojects. For example, consider a web application repository holding different sub packages like frontend, backend and client:
Each subpackage has its own versioning and its version may change independently of other packages. For this reason, I need a way to have separate release notes for each package.
The current implementation of gitchangelog does not seem to provide a way to solve the problem. Instead, it produces a list of all commits of the repo in chronological order regardless the subpackage each commit comes from.
So, I think having a
--path
command line would allow to produce a separate changelog for each subpackage. I imagine something like this:Also it would be nice if the tool would also look for a .gitchangelog.rc within the provided
path
. This would allow each subpackage to have its own configuration.I found a similiar PR #112 which suggests to hard code the
path
as a config variable in the gitchangelog.rc. However, I think having a--path
command line argument would be much more flexible as it would allow to set the path in runtime depending on the subdirectory. This would allow to build the Release Notes for a specific package whenever there is a release for that packageThe text was updated successfully, but these errors were encountered: