Skip to content

fix: resolve the object type behind modifiers in statement_type - #301

Merged
mergify[bot] merged 1 commit into
mainfrom
devs/sileht/sqlparse-0.6/bump-sqlparse-0-6-0--f5b05d1f
Sep 1, 2026
Merged

fix: resolve the object type behind modifiers in statement_type#301
mergify[bot] merged 1 commit into
mainfrom
devs/sileht/sqlparse-0.6/bump-sqlparse-0-6-0--f5b05d1f

fix: resolve the object type behind modifiers in statement_type

35642ab
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 1, 2026 in 5s

1 rule matches and 3 potential rules

⚠️ The pull request has been closed by GitHub because its commits are also part of another pull request

Rule: request review (request_reviews)

  • -closed
  • -merged
  • not:
    • any of:
      • #approved-reviews-by>=1
      • author = dependabot[bot]
  • #changes-requested-reviews-by=0
  • -author=dependabot[bot]
  • review-requested!=@devs
  • all of:
    • check-success=Test with Python 3.10
    • check-success=Test with Python 3.11
    • check-success=Test with Python 3.12
    • check-success=semgrep

✅ Rule: dismiss reviews (dismiss_reviews)

Rule: warn on conflicts (comment, label)

  • -closed
  • conflict

Rule: label on unresolved (label)

  • #review-threads-unresolved>0

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