🛠 Repo: Don't create release PR until there's a user-facing change?

[JoshuaKGoldberg]

Tooling Suggestion Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have read and agree to Mocha's Code of Conduct and Contributing Guidelines
• I have searched for related issues and issues with the faq label, but none matched my issue.
• I want to provide a PR to resolve this

Overview

Following #5186: we're seeing a release-it PR created when the only commits on main are from chore: ... commits (### 🧹 Chore). #5189 is an example.

I'd think we'd want to skip creating the PR until there's something like a feat or fix that impacts users. Is such a thing doable with release-it?

Additional Info

A note from @voxpelli's #5189 (comment):

@JoshuaKGoldberg We can remove parts by changing / adding / removing to

mocha/.github/release-please/config.json

Lines 5 to 17 in 5c2989f

	"changelog-sections": [
	{ "type": "feat", "section": "🌟 Features", "hidden": false },
	{ "type": "fix", "section": "🩹 Fixes", "hidden": false },
	{ "type": "docs", "section": "📚 Documentation", "hidden": false },
	{ "type": "chore", "section": "🧹 Chores", "hidden": false },
	{ "type": "perf", "section": "🧹 Chores", "hidden": false },
	{ "type": "refactor", "section": "🧹 Chores", "hidden": false },
	{ "type": "test", "section": "🧹 Chores", "hidden": false },
	{ "type": "build", "section": "🤖 Automation", "hidden": false },
	{ "type": "ci", "section": "🤖 Automation", "hidden": true }
	],

[voxpelli]

If we change to "hidden": false we can hide it from the release notes

The default for release-please is actually:

    { type: 'feat', section: 'Features' },
    { type: 'feature', section: 'Features' },
    { type: 'fix', section: 'Bug Fixes' },
    { type: 'perf', section: 'Performance Improvements' },
    { type: 'revert', section: 'Reverts' },
    { type: 'docs', section: 'Documentation', hidden: true },
    { type: 'style', section: 'Styles', hidden: true },
    { type: 'chore', section: 'Miscellaneous Chores', hidden: true },
    { type: 'refactor', section: 'Code Refactoring', hidden: true },
    { type: 'test', section: 'Tests', hidden: true },
    { type: 'build', section: 'Build System', hidden: true },
    { type: 'ci', section: 'Continuous Integration', hidden: true }

[JoshuaKGoldberg]

hide it from the release notes

Ah, we've included chores in the release notes for previous ones...

[voxpelli]

Yeah, I would have wanted a way to say "Don't trigger, but include when triggered by something else"

I would ultimately want to swap to release-it/release-it#1126, whenever I get time to implement that :/

[voxpelli]

If we change to "hidden": false we can hide it from the release notes

The default for release-please is actually:

    { type: 'feat', section: 'Features' },
    { type: 'feature', section: 'Features' },
    { type: 'fix', section: 'Bug Fixes' },
    { type: 'perf', section: 'Performance Improvements' },
    { type: 'revert', section: 'Reverts' },
    { type: 'docs', section: 'Documentation', hidden: true },
    { type: 'style', section: 'Styles', hidden: true },
    { type: 'chore', section: 'Miscellaneous Chores', hidden: true },
    { type: 'refactor', section: 'Code Refactoring', hidden: true },
    { type: 'test', section: 'Tests', hidden: true },
    { type: 'build', section: 'Build System', hidden: true },
    { type: 'ci', section: 'Continuous Integration', hidden: true }

[JoshuaKGoldberg]

hide it from the release notes

Ah, we've included chores in the release notes for previous ones...

[voxpelli]

Yeah, I would have wanted a way to say "Don't trigger, but include when triggered by something else"

I would ultimately want to swap to release-it/release-it#1126, whenever I get time to implement that :/