mainrs / mainrs/git-cm

Allow per-repo installation

Open
#58 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
101
Forks
8
PR merge metrics
No merged PRs in 30d

Description

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](http://commitizen.github.io/cz-cli/#optional-install-and-run-commitizen-locally). That way I could use this alongside [`rusty-hook`](https://crates.io/crates/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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by investigating how git-cm is installed and invoked, then compare the local-install approach used by Commitizen and the rusty-hook integration described in the issue. Done means a repository can invoke git-cm without requiring a global installation.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, rust
Domain
cli, developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.