di-sukharev / di-sukharev/opencommit
[Feature]: flags to circumvent interactivity and predefine choices
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
I'm trying to use opencommit in an automated workflow so I don't want the questions like push? approve message? add files ? etc.
Suggested Solution
flags to define choices
Alternatives
don't suggest push or add files, just do the message.
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
No files, tests, or entry points are identified in the issue. Start by locating the interactive prompts and CLI argument handling, then define how flags should control pushing, approval, file addition, and message generation; done means automated workflows can run without those questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100