Mahlet-Inc / Mahlet-Inc/hobbits
Question about your commitlint + semantic-release setup
- Dominant language
- Python
- Stars
- 751
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Hey @hello-adam, noticed hobbits ships releases off conventional commits via semantic-release, with commitlint enforcing the format. I'm researching how teams keep commit messages consistent. I built a small tool in the space but I'm not selling anything here.
When a contributor's commit doesn't conform, what happens for you? Does it silently drop out of the changelog, block CI, or get fixed by hand afterward? And does that ever cost the team real time? Trying to learn whether this is worth solving. Fine to close if it's noise. Thanks!
Contributor guide
Research direction
No files, tests, or entry points are identified. Clarify the observed commitlint and semantic-release behavior and the desired repository change before implementation; done should be a documented, reproducible outcome.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100