di-sukharev / di-sukharev/opencommit
Commit message longer than 74 characters
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
My commit messages are often longer than 74 characters.
Suggested Solution
I have noticed that the prompt requests messages not exceed 74 characters. Would it be sensible to implement a check that, if a message is longer than 74 characters, prompts the chat to shorten it until it meets this character limit?
Alternatives
No response
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the prompt that requests commit messages and the entry point where the generated message is passed on. Confirm how the 74-character requirement is currently communicated, then define done as handling messages over that limit according to the proposed shortening behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100