di-sukharev / di-sukharev/opencommit
[Feature]: Optout of conventional commits and support Gitmoji spec
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
Currently opencommit supports a variant of Conventional Commits and Gitmoji.
This is incompatible with projects that use Gitmoji.
In the context of Gitmoji, the emoji already provides enough context as to what the commit is about. Titles should also use sentence case.
Suggested Solution
This is the correct format of Gitmoji commits.
<intention> [scope?][:?] <message>
intention: An emoji from the list.
scope: An optional string that adds contextual information for the scope of the change.
message: A brief explanation of the change.
Examples:
✏️ Update the name attribute of 💫
🔧 Change Dependabot interval to monthly
⬆️ Bump prettier from 2.8.8 to 3.0.0 (#1529)
See Gitmoji
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
No files, tests, or configuration entry points are named in the issue. Start by locating the commit-message generation and Conventional Commits configuration, then determine how opt-out behavior should be exposed. Done means Gitmoji-formatted, sentence-case messages are supported without requiring Conventional Commits, with coverage for the stated examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100