Skip to content

Python: Migrate to use "implicit namespace packages" (PEP 420)

7034388
Select commit
Loading
Failed to load commit list.
Merged

Python: Migrate to use "implicit namespace packages" (PEP 420) #448

Python: Migrate to use "implicit namespace packages" (PEP 420)
7034388
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 Nov 4, 2024 in 0s

1 potential rule

⚠️ The pull request has been merged by @amotl

‼️ Action Required ‼️

The configuration uses the deprecated merge_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
A brownout is planned on September 16th, 2024.
This option will be removed on October 21st, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: automatic merge (queue)

  • -closed [📌 queue requirement]
  • label=ready-to-merge
  • status-success~=^Build & publish package to pypi
  • status-success~=^Test python
  • #approved-reviews-by>=1
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • status-success~=^Build docs on macos-latest
  • status-success~=^Build docs on ubuntu-latest
  • status-success~=docs/readthedocs.org
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • 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 repository ruleset rule]
        • check-success = verification/cla-signed
        • check-neutral = verification/cla-signed
        • check-skipped = verification/cla-signed

💖  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