-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: reduce list of releasable tags to feat
, fix
and perf
#68
Conversation
.github/workflows/release-please.yml
Outdated
{ "type": "ci", "section": "Chores", "hidden": false }, | ||
{ "type": "refactor", "section": "Chores", "hidden": false }, | ||
{ "type": "test", "section": "Chores", "hidden": false } | ||
{ "type": "perf", "section": "Chores", "hidden": false } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we maybe rename this section to "Performance Improvements"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renamed in a1722cf
By testing in a test repo, it seems that it won't close the existing release PR. But we could close it manually & remove the label & delete the branch, and next time we commit a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Yes, I think it will probably close the PR as it does seem to update with every commit. Interested to see...
It didn't close the PR. Looks like it found there are no releasable commits and decided that there's no further action needed :)
I'll remove the label, close the PR, and delete the branch. |
Per eslint/eslint#18455, only commits tagged as
feat
,fix
, orperf
should trigger a release.This PR removes all other tags from
changelog-types
in the release-please configuration.This means that release-please will no longer consider commits tagged as
docs
,build
,chore
,ci
,refactor
, ortest
as "releasable units" and will thus no longer create a release PR for those commits. Note that this also means that those commits won't be included in the changelog.I'm not sure what will release-please do with #65 after we merge this. Since there are no "releasable units" committed at the moment, perhaps it will close the PR?