di-sukharev / di-sukharev/opencommit

[Feature]: Support only one line commit message and adjustment type

Open
#409 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
7.5k
Forks
445
Avg merge
18m
Merged PRs (30d)
2

Description

Description
  1. The current commit is divided into individual messages for each file, but sometimes the entire function will affect different files. I hope there is only a single line of commit message that includes the results of multiple files combined.

  2. Also, sometimes the type of commit judged by OCO differs from my perception. I hope there can be an option to choose what type of current commit it is, such as OCO thinks it's a fix but I might think it's a feat.

Suggested Solution

The current format is:

fix (filename): description
feat (filename): description

I hope it can be changed to:

fix: description of all of the files

Assume the current result generated by OCO is:

fix (filename): description

I hope it can be adjusted to other types, such as:

feat (filename): description
Alternatives

No response

Additional Context

No response

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

The issue does not name files or tests. Start by locating the code that generates per-file commit messages and determines the commit type, then trace how the generated result reaches the CLI. Done means supporting one combined message and allowing the user to adjust the suggested type, with coverage for both behaviors.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, javascript
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.