We have excludeScopes which is nice, but the opposite would be quite useful for monorepos.
includeScopes should accept a list of scopes which will filter the changelist of the changelog.
This is useful in monorepo setups, where you have different releases for different parts of the project. The tagFrom and tagTo are already quite useful because you can filter for subproject-v0.1.1 to subproject-v0.1.0. However, right now every release shows either all scopes (even if a commit didn't affect a certain release) or I can exclude the others, which woudl require to build a list of all subprojects and then removing the current one. With includeScopes I could just set that to includeScopes: subproject,ci and it would filter for my project (and optinally other generic scopes).
We have
excludeScopes
which is nice, but the opposite would be quite useful for monorepos.includeScopes
should accept a list of scopes which will filter the changelist of the changelog.This is useful in monorepo setups, where you have different releases for different parts of the project. The tagFrom and tagTo are already quite useful because you can filter for
subproject-v0.1.1
tosubproject-v0.1.0
. However, right now every release shows either all scopes (even if a commit didn't affect a certain release) or I can exclude the others, which woudl require to build a list of all subprojects and then removing the current one. WithincludeScopes
I could just set that toincludeScopes: subproject,ci
and it would filter for my project (and optinally other generic scopes).