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

Bump setuptools from 75.2.0 to 75.3.0 in /requirements #1712

Merged
merged 1 commit into from
Oct 29, 2024

Bump setuptools from 75.2.0 to 75.3.0 in /requirements

60f28c8
Select commit
Loading
Failed to load commit list.
Merged

Bump setuptools from 75.2.0 to 75.3.0 in /requirements #1712

Bump setuptools from 75.2.0 to 75.3.0 in /requirements
60f28c8
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 29, 2024 in 0s

4 potential rules

‼️ 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: Dependency updater - automatic merge on CI passing (delete_head_branch)

  • -merged
  • author~=^(pyup-bot|dependabot\[bot\])$
  • closed [📌 delete_head_branch requirement]
  • status-success=test (3.x, 12, lint)
  • status-success=test (3.x, 12, py3-cov)

Rule: Dependency updater - automatic merge on CI passing (queue)

  • -closed [📌 queue requirement]
  • -merged
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • author~=^(pyup-bot|dependabot\[bot\])$
  • status-success=test (3.x, 12, lint)
  • status-success=test (3.x, 12, py3-cov)
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-success = test (3.x, 12, lint)
        • check-neutral = test (3.x, 12, lint)
        • check-skipped = test (3.x, 12, lint)
      • any of: [🛡 GitHub branch protection]
        • check-success = test (3.x, 12, py3-cov)
        • check-neutral = test (3.x, 12, py3-cov)
        • check-skipped = test (3.x, 12, py3-cov)

Rule: Automatic merge on approval (delete_head_branch)

  • #approved-reviews-by>=1
  • label=ready to merge
  • #changes-requested-reviews-by=0
  • closed [📌 delete_head_branch requirement]

Rule: Automatic merge on approval (queue)

  • #approved-reviews-by>=1
  • -closed [📌 queue requirement]
  • label=ready to merge
  • #changes-requested-reviews-by=0
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-success = test (3.x, 12, lint)
        • check-neutral = test (3.x, 12, lint)
        • check-skipped = test (3.x, 12, lint)
      • any of: [🛡 GitHub branch protection]
        • check-success = test (3.x, 12, py3-cov)
        • check-neutral = test (3.x, 12, py3-cov)
        • check-skipped = test (3.x, 12, py3-cov)

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

🚀  You can help us by becoming a sponsor!


2 not applicable rules

Rule: Dependency updater - flag for human review on coverage failing (comment, request_reviews)

  • -merged
  • author~=^(pyup-bot|dependabot)$
  • status-failure=test (3.x, 12, py3-cov)

Rule: Dependency updater - flag for human review on lint failing (comment, request_reviews)

  • -merged
  • author~=^(pyup-bot|dependabot)$
  • status-failure=test (3.x, 12, lint)
  • -status-failure=test (3.x, 12, py3-cov)
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