mapbox / mapbox/github-release-tools
Is including tags in changelog-draft output really useful?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
* `feature` and `bug` are implied given their presence in the relevant section
* `under development` should not be included (it's incorrect)
* `needs discussion` should not be included (same)
* `good first issue` seems irrelevant for changelog purposes
Seems like we should just drop this part of the output.
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
Start by locating the changelog-draft implementation and inspect how issue tags are included in its output. Remove the tag section so implied, incorrect, and irrelevant tags are omitted, then verify that the generated changelog output no longer contains them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100