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

fix(tinmu): fix tianmu crash when set varchar to num when order by #1807

Merged
merged 1 commit into from
May 22, 2023

fix(tinmu): fix tianmu crash when set varchar to num when order by

5467091
Select commit
Loading
Failed to load commit list.
Merged

fix(tinmu): fix tianmu crash when set varchar to num when order by #1807

fix(tinmu): fix tianmu crash when set varchar to num when order by
5467091
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded May 22, 2023 in 4s

3 rules match and 11 potential rules

Rule: automatic merge of hotfix (high priority) (queue)

  • label=PR-bug
  • #approved-reviews-by>=2
  • #approved-reviews-by>=2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -draft [:pushpin: queue requirement]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • check-success~=^stonedb-build(.*)
  • label!=PR-docs

Rule: put other pr to merge queue (queue)

  • #approved-reviews-by>=2
  • #approved-reviews-by>=2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -draft [:pushpin: queue requirement]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • check-success~=^stonedb-build(.*)
  • label!=PR-bug
  • label!=PR-docs

Rule: put docs to merge queue (queue)

  • label=PR-docs
  • #approved-reviews-by>=2
  • #approved-reviews-by>=2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -draft [:pushpin: queue requirement]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]

Rule: Comment PR if title not semantic (comment)

  • -title~=^(feat|fix|docs|workflow|perf|style|refactor|test|website|chore)(\(.*\))?:
  • author!=Mergify

Rule: ping author if there is conflicts (comment)

  • conflict
  • #approved-reviews-by >= 2

Rule: Welcome new contributor (comment)

  • author!=Mergify

Rule: label on New Feature (label)

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

Rule: label on Bug Fix (label)

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

Rule: label on docs (label)

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

Rule: label on perf (label)

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

Rule: label on style (label)

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

Rule: label on Refactor (label)

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

Rule: label on test (label)

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

Rule: label on chore (label)

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

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


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