Is your feature request related to a problem? Please describe.
We are generating a centralized changelog for different sub-projects within a monorepo. At present, we're using --include-path to generate N separate changelogs.
However, a given commit can span multiple sub-projects, and the total "changelog" produced by unioning each individual path's result can be long and contain a lot of duplication.
I can see a few different ways of enabling the above workflow to produce a result that's much more compact.
Describe the solution you'd like
The ability to annotate "named paths" and have that be accessible inside the "context".
producing a "named-paths": ["Foo", "Bar", "Baz"] in the context, enabling one to customize the template to render those paths alongside each commit line-item in their respective sections
The ability to execute git-cliff against externally deserialized context
git-cliff --include-path lib/foo --output foo.json
git-cliff --include-path lib/bar --output bar.json
# jq magic that deduplicates commits and annotates them in some way that does something like the above
git-cliff --from-context combined-context.json
The ability to --include-paths multiple times (supported already), but expose the (full set of) matched paths to the context, for similar reasons to option 1.
Is your feature request related to a problem? Please describe.
We are generating a centralized changelog for different sub-projects within a monorepo. At present, we're using
--include-path
to generate N separate changelogs.However, a given commit can span multiple sub-projects, and the total "changelog" produced by unioning each individual path's result can be long and contain a lot of duplication.
I can see a few different ways of enabling the above workflow to produce a result that's much more compact.
Describe the solution you'd like
The ability to annotate "named paths" and have that be accessible inside the "context".
producing a
"named-paths": ["Foo", "Bar", "Baz"]
in the context, enabling one to customize the template to render those paths alongside each commit line-item in their respective sectionsThe ability to execute
git-cliff
against externally deserialized contextThe ability to
--include-paths
multiple times (supported already), but expose the (full set of) matched paths to the context, for similar reasons to option 1.