ci(release): lint readme and changelog before committing #6406
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 January Priorities Patch - Bugs only milestone
benelan
added a commit
that referenced
this pull request
Feb 8, 2023
**Related Issue:** #6406 ## Summary The commit messages for `next` releases are goofed. This removes our custom `{{currentTag}}` commit message and replaces it with the default: `chore(release): {{currentTag}}` It also removes `noVerify` so we can remove `npm run lint:md` from standard-version's pre-commit hook because it will be done by `lint-staged`. The commit message was fine before the PR linked above. No idea why this is happening but it's probably a `standard-version` bug.
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: #6355
Summary
I added markdown lint in the PR above but it isn't running during releases because we have
standard-versionset tonoVerify. So this is manually linting the readme/changelog before committing.