di-sukharev / di-sukharev/opencommit
Feature: Commit-message Prefix
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
We use semanic branchnames like:
feature/PROJECT-123-a-nice-new-feature or bug/PROJECT-456-oh-no-a-bug that will contain the Project ID and its Ticket Number.
The Project ID and Ticket-number are also referenced in the Commits, making it easy to link them in the Ticket. So a commit would look like the following:
PROJECT-123
chore(package.json) updates some dependencies.
feat(src/components/someComponent.tsx) Implement awesome feature
It would be nice to be able to do that with opencommit
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 does not name an implementation file or test; it only gives package.json and src/components/someComponent.tsx as examples of commit-message scopes. Start by tracing how opencommit builds commit messages and where branch names or commit prefixes could be read. Done means generated messages consistently include the requested Project ID and ticket-number prefix.
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