semantic-release / semantic-release/release-notes-generator

Question: how can i gruop no-scope commits on a section in release notes generator configuration ?

Open
#611 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
368
Forks
55
Avg merge
10m
Merged PRs (30d)
1

Description

im using this configuration that group certain types of scoped commits but i need to group the non-scoped commits
example non scoped message --> "commit message: this is an non scoped message for this commit",
example scoped message --> "commit message: feat: adding example scoped message for this commit"
i need to group non scoped messages in release note generator section. ¿is it posibble?
configuration:
[
"@semantic-release/release-notes-generator", {
"preset": "conventionalcommits",
"presetConfig": {
"types": [
{ "type": "breaking", "section": "Major version release", "hidden": false },
{ "type": "BREAKING", "section": "Major version release", "hidden": false },
{ "type": "BREAKING CHANGE", "section": "Major version release", "hidden": false },
{ "type": "BREAKING CHANGES", "section": "Major version release", "hidden": false },
{ "type": "feat", "section": "Features", "hidden": false },
{ "type": "fix", "section": "Bug Fixes", "hidden": false },
{ "type": "hotfix", "section": "Bug Fixes", "hidden": false },
{ "type": "update", "section": "Updates", "hidden": false },
{ "type": "upgrade", "section": "Upgrades", "hidden": false },
{ "type": "docs", "section": "Documentation", "hidden": false },
{ "type": "chore", "section": "Chores", "hidden": false },
{ "type": "build", "section": "CI/CD Changes", "hidden": false },
{ "type": "ci", "section": "CI/CD Changes", "hidden": false },
{ "type": "test", "section": "Tests", "hidden": false },
{ "type": "refactor", "section": "Refactoring", "hidden": false },
{ "type": "perf", "section": "Performance Improvements", "hidden": false }
]
},
"writerOpts": {
"commitsSort": ["subject", "scope"]
}
}
]

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the shown @semantic-release/release-notes-generator configuration and its conventionalcommits preset, especially presetConfig.types and writerOpts. Check how commits without a scope are classified, and consider the work done when such commits can consistently appear under a dedicated release-notes section.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.