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

Use NullPool for sqlalchemy engine #5592

Closed
wants to merge 1 commit into from

Use NullPool for sqlalchemy engine

7a9d7fc
Select commit
Loading
Failed to load commit list.
Closed

Use NullPool for sqlalchemy engine #5592

Use NullPool for sqlalchemy engine
7a9d7fc
Select commit
Loading
Failed to load commit list.
This check has been archived and is scheduled for deletion. Learn more about checks retention
Mergify / Summary succeeded Jan 27, 2024 in 2s

5 potential rules

Rule: default (queue)

  • -draft
  • -draft [📌 queue requirement]
  • approved-reviews-by=@fedora-infra/bodhi
  • label!=WIP
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=DCO
        • check-neutral=DCO
        • check-skipped=DCO
      • any of: [🛡 GitHub branch protection]
        • check-success=Build Documentation (pip)
        • check-neutral=Build Documentation (pip)
        • check-skipped=Build Documentation (pip)
      • any of: [🛡 GitHub branch protection]
        • check-success=Diff-cover check
        • check-neutral=Diff-cover check
        • check-skipped=Diff-cover check
      • any of: [🛡 GitHub branch protection]
        • check-success=Pre-commit checks
        • check-neutral=Pre-commit checks
        • check-skipped=Pre-commit checks
      • any of: [🛡 GitHub branch protection]
        • check-success=Unit Tests (pip, bodhi-client)
        • check-neutral=Unit Tests (pip, bodhi-client)
        • check-skipped=Unit Tests (pip, bodhi-client)
      • any of: [🛡 GitHub branch protection]
        • check-success=Unit Tests (pip, bodhi-messages)
        • check-neutral=Unit Tests (pip, bodhi-messages)
        • check-skipped=Unit Tests (pip, bodhi-messages)
      • any of: [🛡 GitHub branch protection]
        • check-success=Unit Tests (pip, bodhi-server)
        • check-neutral=Unit Tests (pip, bodhi-server)
        • check-skipped=Unit Tests (pip, bodhi-server)
      • any of: [🛡 GitHub branch protection]
        • check-success=Build Documentation (f38)
        • check-neutral=Build Documentation (f38)
        • check-skipped=Build Documentation (f38)
      • any of: [🛡 GitHub branch protection]
        • check-success=Unit Tests (f38, bodhi-client)
        • check-neutral=Unit Tests (f38, bodhi-client)
        • check-skipped=Unit Tests (f38, bodhi-client)
      • any of: [🛡 GitHub branch protection]
        • check-success=Unit Tests (f38, bodhi-messages)
        • check-neutral=Unit Tests (f38, bodhi-messages)
        • check-skipped=Unit Tests (f38, bodhi-messages)
      • any of: [🛡 GitHub branch protection]
        • check-success=Unit Tests (f38, bodhi-server)
        • check-neutral=Unit Tests (f38, bodhi-server)
        • check-skipped=Unit Tests (f38, bodhi-server)
      • any of: [🛡 GitHub branch protection]
        • check-success=Build Documentation (f39)
        • check-neutral=Build Documentation (f39)
        • check-skipped=Build Documentation (f39)
      • any of: [🛡 GitHub branch protection]
        • check-success=Unit Tests (f39, bodhi-client)
        • check-neutral=Unit Tests (f39, bodhi-client)
        • check-skipped=Unit Tests (f39, bodhi-client)
      • any of: [🛡 GitHub branch protection]
        • check-success=Unit Tests (f39, bodhi-messages)
        • check-neutral=Unit Tests (f39, bodhi-messages)
        • check-skipped=Unit Tests (f39, bodhi-messages)
      • any of: [🛡 GitHub branch protection]
        • check-success=Unit Tests (f39, bodhi-server)
        • check-neutral=Unit Tests (f39, bodhi-server)
        • check-skipped=Unit Tests (f39, bodhi-server)
  • #changes-requested-reviews-by=0
  • status-success=Build Documentation (f38)
  • status-success=Build Documentation (f39)
  • status-success=Build Documentation (pip)
  • status-success=DCO
  • status-success=Diff-cover check
  • status-success=Integration Tests (f38)
  • status-success=Integration Tests (f39)
  • status-success=Pre-commit checks
  • status-success=Unit Tests (f38, bodhi-client)
  • status-success=Unit Tests (f38, bodhi-messages)
  • status-success=Unit Tests (f38, bodhi-server)
  • status-success=Unit Tests (f39, bodhi-client)
  • status-success=Unit Tests (f39, bodhi-messages)
  • status-success=Unit Tests (f39, bodhi-server)
  • status-success=Unit Tests (pip, bodhi-client)
  • status-success=Unit Tests (pip, bodhi-messages)
  • status-success=Unit Tests (pip, bodhi-server)
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

Rule: backport 7.0 (backport)

  • -draft
  • label!=WIP
  • label=7.0-backports
  • merged [📌 backport requirement]

Rule: backport 7.1 (backport)

  • -draft
  • label!=WIP
  • label=7.1-backports
  • merged [📌 backport requirement]

Rule: backport 7.2 (backport)

  • -draft
  • label!=WIP
  • label=7.2-backports
  • merged [📌 backport requirement]

Rule: backport 8.0 (backport)

  • -draft
  • label!=WIP
  • label=8.0-backports
  • merged [📌 backport requirement]

💖  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