di-sukharev / di-sukharev/opencommit
[Feature]: generate squash message
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
On repositories that only allow squashed merges into the main branch, the history can quickly become hard to read—even when using the conventional commits standard. It would be very helpful if opencommit supported generating a single commit message for a squashed commit.
Suggested Solution
This could be implemented as a new CLI parameter that takes a commit range and produces one combined message. Another useful option would be to support interactive rebases, for example by hooking into prepare-commit-msg during squash operations.
Alternatives
Asking LLM to generate a message based on a list of commits.
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
The issue names no files or tests; start by locating the CLI argument handling and the prepare-commit-msg integration used during squash operations. Clarify whether completion means generating one message from a commit range, supporting interactive rebases, or both, then add coverage for the selected workflow and its resulting combined message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100