di-sukharev / di-sukharev/opencommit
[Feature]: Allow user to edit commit message before commiting
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
The commit message sometimes don't match with the purpose of the commit.
Example:
updating the base image of a Dockerfile generates:
🔨 chore(Dockerfile): update base image to cypress/browsers:node16.16.0-chrome107-ff107 to match Cypress version
I would like to edit this commit message before confirming the commit to:
🔨 chore(Dockerfile): update base image to cypress/browsers:node16.16.0-chrome107-ff107 to match Cypress version
Suggested Solution
Update the 'Confirm the commit message' promt to Yes / No / Edit message instead of Yes / No
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 CLI prompt that confirms the generated commit message and the code that handles the Yes/No response. Add an Edit message choice and verify that the edited text is used when the commit is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100