Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Is including tags in changelog-draft output really useful?

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
release

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.

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.

Dominant language
JavaScript
Stars
16
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/github-release-tools

All issues in mapbox/github-release-tools

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.