-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
fix(actions): ♻️ rebuild ci publish system #63
Conversation
Prettier changelog content to reader format. ref: vivaxy#59
@vivaxy I test in my fork repo and will also push any commit in fork repo in the future in case that I push a mistake to commit. I also add the tag in the steps, it works well except for the publishing which I can not test. See in https://github.com/yi-Xu-0100/vscode-conventional-commits/releases/tag/v1.17.0 If there are no more suggestions for the steps, I will squash and merge the PR and will test to publish a patch version. 😀 |
Awesome! I have no more questions. |
The
release
workflow will run with the follow steps by trigger manually:package.json
and write change log withstandard-version
.CHANGELOG.md
, push the commit, and add a tag..vsix
.CHANGELOG.md
by usingmindsers/changelog-reader-action
.Other changes:
CHANGELOG.md
into.prettierignore
.deploy
for publish.version
.release
.sed 's/^### \[/## [/' -i CHANGELOG.md
to change the changelog content, because it will make content to fit the markdown rules.yarn prettier --write CHANGELOG.md --prose-wrap never --ignore-path ./gitignore
to pretty the format ofCHANGELOG.md
, and it will make content to fill correcttly with the release body.Close #59