Skip to content
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

feat(query): use arrow-rs write parquet #11473

Closed
wants to merge 19 commits into from

Merge branch 'main' into encoding

1fd7414
Select commit
Failed to load commit list.
Closed

feat(query): use arrow-rs write parquet #11473

Merge branch 'main' into encoding
1fd7414
Select commit
Failed to load commit list.
Mergify / Summary succeeded May 29, 2023 in 3s

4 rules match and 11 potential rules

Rule: Put into shared queue (queue)

  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #approved-reviews-by>=2
  • -draft
  • -draft [:pushpin: queue requirement]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • label!=pr-doc
  • label!=pr-rfc

Rule: Put into rfc queue (queue)

  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #approved-reviews-by>=3
  • -draft
  • -draft [:pushpin: queue requirement]
  • label=pr-rfc
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • check-success=Vercel

Rule: Put into docs queue (queue)

  • #approved-reviews-by>=1
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • -draft
  • -draft [:pushpin: queue requirement]
  • label=pr-doc
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • check-success=Vercel

Rule: Check PR conflicts (post_check)

  • -conflict

Rule: Check PR description (comment)

  • -body~=I hereby agree to the terms of the CLA available at: https:\/\/databend\.rs\/dev\/policies\/cla\/
  • -body~=Summary
  • -draft
  • author!=Mergify

Rule: CLA Check (post_check)

  • any of:
    • all of:
      • body~=I hereby agree to the terms of the CLA available at: https:\/\/databend\.rs\/dev\/policies\/cla\/
      • body~=Summary
    • author=Mergify

Rule: Comment PR if title not semantic (comment)

  • -draft
  • -title~=^(rfc|feat|fix|refactor|ci|docs|chore)(\(.*\))?:
  • author!=Mergify

Rule: Semantic PR Check (post_check)

  • any of:
    • title~=^(rfc|feat|fix|refactor|ci|docs|chore)(\(.*\))?:
    • author=Mergify

Rule: label on RFCs (label)

  • title~=^(rfc)(\(.*\))?:

Rule: label on New Feature (label)

  • title~=^(feat)(\(.*\))?:

Rule: label on Bug Fix (label)

  • title~=^(fix)(\(.*\))?:

Rule: label on Refactor (label)

  • title~=^(refactor)(\(.*\))?:

Rule: label on Build/Testing/CI (label)

  • title~=^(ci)(\(.*\))?:

Rule: label on Documentation (label)

  • title~=^(docs)(\(.*\))?:

Rule: label on Not for changelog (label)

  • title~=^(chore)(\(.*\))?:

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com