Mechanism to keep a better Changelog
Open
- Dominant language
- Clojure
- Stars
- 23
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice if it automatically summarize the PRs.
As far as breaking API changes (especially subtle semantics), I'm not sure how best to make sure we don't forget those.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. First clarify the desired changelog source, how PRs should be summarized, and how breaking or subtle API changes should be captured; define the workflow and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100