Skip to content
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

Allow per-repo installation #58

Open
caass opened this issue Mar 22, 2021 · 1 comment
Open

Allow per-repo installation #58

caass opened this issue Mar 22, 2021 · 1 comment

Comments

@caass
Copy link

caass commented Mar 22, 2021

It would be nice if I could check in git-cm along with my other dev dependencies instead of relying on a global install, kind of like how Commitizen allows. That way I could use this alongside rusty-hook to automate creating conventional commits in my repo without telling users to globally install git-cm. I'm not sure if this is something that's possible (installing per-project binaries), but it would be nice to have.

@mainrs
Copy link
Owner

mainrs commented Mar 22, 2021

Good question! I imagined git-cm to be a complete replacement for the commitizen CLI as JS runs really slow on my potato laptop. The plan is to also have a configuration file instead of relying on Cargo.toml to make it possible to use it in other projects as well.

I am not sure if that is actually possible. dev-dependencies are only included when compiling the examples, tests or benchmarks 🤔 It's just the difference in the ecosystem I guess...

The project gets some traction back, I definitely need to finish the whole conventional commits suite of binaries, like the changelog generator and the semantic-release equivalent. Although I use them, the code is still pretty rough and a cleanup is needed :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants