mainrs / mainrs/git-cm

[Feature Request] Support config through a unified file

Open
#29 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

As of now, commit types can be specified in `Cargo.toml`, which works fine for Rust projects. However, this isn't suitable in non-Rust projects.

I'd like to suggest using a unified config file everywhere, say `git-cm.toml` or (whatever file type is preferable for parsing) for easy use of `git-cm` regardless of the project.

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

Start by locating how commit types are currently read from Cargo.toml. Review the existing configuration path before deciding how a unified file should be parsed and where it should be discovered. Done means non-Rust projects can configure git-cm while existing Rust-project behavior remains supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.