Open JoshuaKGoldberg opened 3 months ago
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 }
hide it from the release notes
Ah, we've included chores in the release notes for previous ones...
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 https://github.com/release-it/release-it/issues/1126, whenever I get time to implement that :/
Tooling Suggestion Checklist
main
branch of the repository.faq
label, but none matched my issue.Overview
Following #5186: we're seeing a release-it PR created when the only commits on
main
are fromchore: ...
commits (### 🧹 Chore
). #5189 is an example.I'd think we'd want to skip creating the PR until there's something like a
feat
orfix
that impacts users. Is such a thing doable with release-it?Additional Info
A note from @voxpelli's https://github.com/mochajs/mocha/pull/5189#issuecomment-2271538878: