Replies: 2 comments 3 replies
-
|
LGTM, Would we consider adding a copy of |
Beta Was this translation helpful? Give feedback.
1 reply
-
Which part of the PR does it extract keywords from? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Background
fusebotsused to help us make releases every day. However, we don't want to maintain an extra service after the adoption of mergify. Instead, we want to generate changelogs and upload releases via GitHub actions instead.Also, our community has a need for
semantic releasewhich allows us to generate more user-friendly releases which containrefactororbugfix.Proposal
So I propose to change our release process in the following ways:
Enable semantic PRs
We will adopt semantic PR via
mergify: all PR's titles should carry a tag. PRs that do not carry tags will be rejected bymergifyWithin this change:
Changelogin the PR description: they will be inferred by PR's tagpr-bugfixvia PR's tagFor example:
bugfix: show query with limit will failed whend enable planner v2will be labeled aspr-bugfixand recorded asBugfixin changedlogfeat(ast): add span info for TableReferencewill be labeled aspr-featand recorded asNew Featuresin the changelogci: Upgrade rust versionwill be labeled aspr-buildand ignored in changelogEnable semantic release
We will make release notes via GitHub native API: Automatically generated release notes.
By maintaining
.github/release.yml, we will generate changelogs by labels of PRs.Retional
Why not
semantic-release?semantic-release is a great project but:
package.json)Valid tags
feat: this PR introduces a new feature to the codebasefix: this PR patches a bug in codebaserefactor: this PR changes the code base without new features or bugfixci|build: this PR changes build/testing/ci stepsdocs|website: this PR changes the documents or websiteschore: this PR only has small changes that no need to record, like coding styles.Beta Was this translation helpful? Give feedback.
All reactions