di-sukharev / di-sukharev/opencommit
[Feature]: Add prefix option for commit messages
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
Hi @di-sukharev,
Thanks for this wonderful tool.
It would be great to have the option to define a custom prefix message for the commits.
Suggested Solution
Something like:
custom-message: JIRA#
custom-message: AB#
custom-message: GI#
Alternatives
- https://github.com/di-sukharev/opencommit/issues/107
- https://github.com/di-sukharev/opencommit/issues/59
- https://github.com/di-sukharev/opencommit/issues/45
Additional Context
This will allow us to pass the commit message validator in our CI pipelines. For e.g. in our team, we use Azure Board for defining commit messages.
AB#0 feat(back): add new backend module
Since this tool is already using the conventional commits standard, would be great to have an option to include our specific project prefix in the tool.
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 tracing the CLI configuration and commit-message generation entry points. Define how a custom prefix is configured and combined with conventional commits, then verify that generated messages include the requested prefix, such as AB#0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100