Add option to make changelog via git graph analysis
- Dominant language
- Go
- Stars
- 65
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Today the changelog is generated from the set of closed issues or merged PRs between two timestamps. This sometimes causes issues, but also does not allow for non-trivial release configurations. Can you add a mode that a user could enable that swaps this "chronological" approach with a git graph analysis? This would require only allowing for merged PRs and issues attached to them.
Contributor guide
Research direction
The issue does not name files, tests, or entry points. Start by tracing the existing timestamp-based changelog generation and configuration, then identify how merged PRs and their attached issues are collected. Done means users can enable a git-graph mode that limits changelog entries to merged PRs and attached issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, go
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100