We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Instead of having to execute commands, like so:
git cliff --include-path "projects/rawkode.academy/zulip/**/*" --repository ../../../
I'd like to instead have a cliff.yaml nested throughout my monorepository that allows me to segment my monorepository.
cliff.yaml
Adding a cliff.yaml to a directory should automatically set --include-paths to that directory and lower.
--include-paths
git-cliff should always use the Git root as --repository
--repository
N/A
No response
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️
Sorry, something went wrong.
Hey, thanks for creating the issue! 👋🏼
I generally agree that the monorepo support should be improved.
I created #975 which fixes that, no need to do --repository ../../ etc. anymore!
--repository ../../
Done in #976
Let me know if you can test this out! I'd appreciate some help to see if the behavior is correct now :)
Awesome. I'll run some tests tonight.
Thank you!
orhun
No branches or pull requests
Is there an existing issue or pull request for this?
Feature description
Instead of having to execute commands, like so:
git cliff --include-path "projects/rawkode.academy/zulip/**/*" --repository ../../../
I'd like to instead have a
cliff.yaml
nested throughout my monorepository that allows me to segment my monorepository.Desired solution
Adding a
cliff.yaml
to a directory should automatically set--include-paths
to that directory and lower.git-cliff should always use the Git root as
--repository
Alternatives considered
N/A
Additional context
No response
The text was updated successfully, but these errors were encountered: