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

Add simultaneous support for Werkzeug 2 and 3 #1378

Closed

Add simultaneous support for Werkzeug 2 and 3

699dfb5
Select commit
Failed to load commit list.
Closed

Add simultaneous support for Werkzeug 2 and 3 #1378

Add simultaneous support for Werkzeug 2 and 3
699dfb5
Select commit
Failed to load commit list.
Mergify / Summary succeeded Mar 14, 2024 in 1s

1 rule matches and 4 potential rules

Rule: automatic merge (queue)

  • #approved-reviews-by>=1
  • check-success=test (py39, mysql-ceph)
  • check-success=test (py39, mysql-ceph-upgrade-from-4.4)
  • check-success=test (py39, mysql-s3)
  • check-success=test (py39, postgresql-ceph)
  • check-success=test (py39, postgresql-s3)
  • check-success=test (py39, postgresql-swift)
  • -draft [📌 queue requirement]
  • check-success=check (build)
  • check-success=check (pep8)
  • check-success=doc (docs)
  • check-success=doc (docs-gnocchi-web)
  • check-success=test (py311, mysql-file)
  • check-success=test (py311, mysql-file-sqlalchemy14)
  • check-success=test (py311, mysql-s3)
  • check-success=test (py311, mysql-swift)
  • check-success=test (py311, postgresql-file)
  • check-success=test (py311, postgresql-file-sqlalchemy14)
  • check-success=test (py311, postgresql-file-upgrade-from-4.4)
  • check-success=test (py311, postgresql-s3)
  • check-success=test (py311, postgresql-swift)
  • check-success=test (py39, mysql-file)
  • check-success=test (py39, mysql-file-sqlalchemy14)
  • check-success=test (py39, mysql-swift)
  • check-success=test (py39, postgresql-file)
  • check-success=test (py39, postgresql-file-sqlalchemy14)
  • check-success=test (py39, postgresql-file-upgrade-from-4.4)
  • label!=work-in-progress
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]

✅ Rule: dismiss reviews on additional commit (dismiss_reviews)

Rule: backport stable/4.4 (backport)

  • label=backport-to-4.4
  • merged [📌 backport requirement]

Rule: backport stable/4.5 (backport)

  • label=backport-to-4.5
  • merged [📌 backport requirement]

Rule: backport stable/4.6 (backport)

  • label=backport-to-4.6
  • merged [📌 backport requirement]

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

🚀  You can help us by becoming a sponsor!


1 not applicable rule

Rule: automatic merge backports from Mergify (queue)

  • author=mergify[bot]
  • -draft [📌 queue requirement]
  • base~=^stable/.*
  • label!=work-in-progress
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of [📌 queue conditions of queue default]
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