Question: How does the `uncategorized` work?

[raminqaf]

Hi,
How does the newly included uncategorized section work? Is it configurable? For instance, if we want to change the title to something different? I couldn't find any documentation of it.

#1137

[mikepenz]

Good day.

It works equally to other categories:

release-changelog-builder-action/src/configuration.ts

Lines 76 to 93 in 6fdcc2d

	categories: [
	{
	title: '## 🚀 Features',
	labels: ['feature']
	},
	{
	title: '## 🐛 Fixes',
	labels: ['fix']
	},
	{
	title: '## 🧪 Tests',
	labels: ['test']
	},
	{
	title: '## 📦 Uncategorized',
	labels: []
	}
	], // the categories to support for the ordering

the main difference is that it will include anything which was missed to be categorised.

If you don't want it, or you want a different title. Configuring the categories will do the track.

E.g. if you don't want this section, you can configure to use the old set of cateogires: https://github.com/mikepenz/release-changelog-builder-action/blob/v3.7.2/src/configuration.ts#L96-L109

[raminqaf]

@mikepenz Thanks for the fast response! 🚀
Actually, we want a section where we put all the PRs that don't contain the labels in the categories. For example, here you have feature, fix, and test. If I have a PR with the labels update-dependencies or ci this should land in the uncategorized one.
However, we want to name the header 🌀 Miscellaneous, instead fo Uncategorized

[mikepenz]

So you can configure it via the categories. Just go with something like:

"categories": [
                {
                    "title": "## 🚀 Features",
                    "labels": ["feature"]
                },
                {
                    "title": "## 🐛 Fixes",
                    "labels": ["fix"]
                },
                {
                    "title": "## 🧪 Tests",
                    "labels": ["test"]
                },
                {
                    "title": "## 🌀 Miscellaneous",
                    "labels": []
                }
 ]

If you don't already have a config you can even define it via the yaml file and don't require a separate json.

https://github.com/mikepenz/release-changelog-builder-action/blob/develop/.github/workflows/ci.yml#L52-L82