di-sukharev / di-sukharev/opencommit
[FEATURE REQUEST] `push` automatically with a config FORCE_PUSH
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
- I do not want to be asked to push commits and do not want the commits pushed by
oc.- Alternatively, some people may want the option to automatically push commits without being asked.
- Some people, not me, but some people may want the commit message used automatically without confirmation.
These all seem like great things to add as options IMHO.
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, tests, or entry points. Begin by locating the oc push and commit-message confirmation flows and the existing configuration handling. Clarify the desired options for automatic pushing, suppressing pushes, and automatic message confirmation; done means the agreed behaviors are configurable and covered by tests or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100