Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement Request: Multi-package repo support #131

Open
sergiosmcr opened this issue May 18, 2020 · 1 comment
Open

Enhancement Request: Multi-package repo support #131

sergiosmcr opened this issue May 18, 2020 · 1 comment

Comments

@sergiosmcr
Copy link

sergiosmcr commented May 18, 2020

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:

gitchangelog --path backend
gitchangelog --path frontend 
gitchangelog --path client

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

@sergiosmcr
Copy link
Author

sergiosmcr commented May 21, 2020

@vaab What do you think of this? I am working on changes for a new PR, but I would like to know your opinion.

I also noticed the last commit was on 2018. Do you still maintain this repo? :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant