Closed anshuldata closed 2 months ago
ACTION NEEDED
Substrait follows the Conventional Commits specification for release automation.
The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification.
@EpsilonPrime I don't have write access to branch. Can you kindly merge ? Thanks
As this PR is somewhere between a new feature and a change to an existing one I'd like to get another approval for this PR before we merge it. I'll check with the other folks at the Substrait community meeting on Wednesday and will likely merge it then.
@anshuldata can you rebase?
@anshuldata can you rebase?
rebased it
Thank you for submitting a PR!
Before you continue, please ensure that your PR title and description (this message!) follow conventional commit syntax. Substrait uses an automated release process that, among other things, uses PR titles & descriptions to build a changelog, so the syntax and format matter!
The title of the PR should be a valid commit header.
Some examples of proper commit message headers and PR titles:
feat: add feature X
fix: X in case of Y
docs: improve documentation for X
Note the case and grammar conventions.
Furthermore, the description of any PR that includes a breaking change should contain a paragraph that starts with
BREAKING CHANGE: ...
, where...
explains what changed. The automated release process uses this to determine how it should bump the version number. Anything that changes the behavior of a plan that was previously legal is considered a breaking change; note that this includes behavior specifications that only exist in Substrait in the form of behavior descriptions on the website or in comments.