ci(next): fix commit message #6425
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
chore
github-actions
bot
added this to the 2023 February Priorities - No breaking changes milestone
benelan
added a commit
that referenced
this pull request
Feb 8, 2023
…c-rulez * origin/master: docs: update component READMEs (#6352) ci(next): fix commit message (#6425) fix(vite): resolve lazying loading error in dist build (#6436) docs(changelog): remove reverted feature (#6435) revert: "feat(pagination, split-button, dropdown, date-picker) action-group): add setFocus method (#6405)" (#6426) 1.1.0-next.2 docs(segmented-control): update event description for calciteSegmentedControlChange (#6428) fix(tree-item): reverses regression to bring back focus when navigating with keyboard (#6424) fix(icon): fix icon normalization to handle x-times-named icons (#6422)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue: #6406
Summary
The commit messages for
nextreleases are goofed. This removes our custom{{currentTag}}commit message and replaces it with the default:chore(release): {{currentTag}}.It also removes
noVerifyso we can removenpm run lint:mdbecause it will be done bylint-staged.The commit message was fine before the PR linked above. No idea why this is happening but it's probably a
standard-versionbug