software-challenge / software-challenge/backend
Auto-generate correct commit messages
Open
Nobody has claimed this yet.
action:implement
component:build
- Dominant language
- HTML
- Stars
- 13
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Based on the changed files, we could infer type & scope in some cases
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 named. Start by locating how commits are created and how changed files are available to that workflow. Define which file patterns map to commit types and scopes, then document a testable set of expected messages before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100