-
-
Notifications
You must be signed in to change notification settings - Fork 204
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
Specify a subpath to build the changelog #11
Comments
Hello, You can do If that's not what you mean, please elaborate. |
Hi,
For now, I usually do Regards, |
I see. Have you tried |
Yes, but I have an error:
|
I think I finally get it 😃 0bb7c91 -> adds e.g. git cliff --commit-path git-cliff-core/ -o git-cliff-core/CHANGELOG.md This argument will be available with the next release. In the meantime feel free to test it out and report bugs if any 🐻 |
|
Previously, cliff was sorting the commits by oldest first. Like: ``` - Support parsing the missing scopes with `default_scope` (orhun#8) - Support generating a changelog scoped to a directory (orhun#11) ``` As the PR numbers indicate, the first bullet point is definitely older than the latter. With this update, it will look like this: ``` - Support generating a changelog scoped to a directory (orhun#11) - Support parsing the missing scopes with `default_scope` (orhun#8) ``` Signed-off-by: Taylan Dogan <[email protected]>
* refactor(changelog): sort commits by newest in CHANGELOG Previously, cliff was sorting the commits by oldest first. Like: ``` - Support parsing the missing scopes with `default_scope` (#8) - Support generating a changelog scoped to a directory (#11) ``` As the PR numbers indicate, the first bullet point is definitely older than the latter. With this update, it will look like this: ``` - Support generating a changelog scoped to a directory (#11) - Support parsing the missing scopes with `default_scope` (#8) ``` Signed-off-by: Taylan Dogan <[email protected]> * refactor: add sorting flag I don't expect any other sorting types will be added so the logic consist of checking whether it is `newest` or not. One could argue with why wouldn't I make this a boolean. My answer would be, in my opinion, it lose its meaning because this is not something we want to enable or disable but something that we want to decide which pattern we want to use. So it is more like a semantic choice. Signed-off-by: Taylan Dogan <[email protected]> * docs(readme): move the explanation of sort flag to README.md Co-authored-by: orhun <[email protected]>
Hi,
In the context of a mono-repo, is it possible to specify the repository subpath to build the changelog from ?
Something like git cliff -- subpath/
Thanks.
The text was updated successfully, but these errors were encountered: