-
-
Notifications
You must be signed in to change notification settings - Fork 283
Question for commit filtering #34
Copy link
Copy link
Closed
Labels
feature/requestNew feature or requestNew feature or requestquestionFurther information is requestedFurther information is requested
Description
Hello, we're evaluating using git-cliff for our monorepo, in order to automate the generation of the CHANGELOG. The tool looks really powerful!
We have a couple of questions:
- is it possible to ignore commits, if they all concern files under a common path? To explain the use case, our monorepo holds both libraries and apps. The apps live under the same folder, "apps". The changelog is only supposed to contain the changes of the libraries, which live in multiple folders. So if a commit only contains changes against paths under "apps/*", we'd like to filter them out if possible.
- is it possible to only process merge commits? We always work with merge requests and this ends up in the default branch as either one squashed commit or multiple commits + merge commit. I believe it is possible in Git to determine if a commit belongs to a merge commit by checking its parents (I don't remember it 100%). Can git-cliff identify and exclude commits that are referenced by a merge commit? Otherwise we'll end up with duplicate messages in the changelog.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
feature/requestNew feature or requestNew feature or requestquestionFurther information is requestedFurther information is requested