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.

Sign up for GitHub

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

Jump to bottom

[pre-commit.ci] pre-commit autoupdate #13230

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

[pre-commit.ci] pre-commit autoupdate

3d3f201
Select commit
Loading
Failed to load commit list.
Open

[pre-commit.ci] pre-commit autoupdate #13230

[pre-commit.ci] pre-commit autoupdate
3d3f201
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 18, 2024 in 1s

1 potential rule

‼️ 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.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: automatic merge for master when CI passes and approved (queue)

  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • #commented-reviews-by=0
  • #review-requested=0
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base=master
  • status-success=jslint
  • status-success=lint
  • status-success=mypy
  • status-success=test
  • 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 = jslint
        • check-neutral = jslint
        • check-skipped = jslint
      • any of: [🛡 GitHub branch protection]
        • check-success = lint
        • check-neutral = lint
        • check-skipped = lint
      • any of: [🛡 GitHub branch protection]
        • check-success = mypy
        • check-neutral = mypy
        • check-skipped = mypy
      • any of: [🛡 GitHub branch protection]
        • check-success = test
        • check-neutral = test
        • check-skipped = test
💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

3 not applicable rules

Rule: automatic merge dependency updates (delete_head_branch)

  • author~=(pyup-bot|dependabot)
  • closed [📌 delete_head_branch requirement]
  • -files~=^(!?.github/workflows/)
  • status-success=jslint
  • status-success=lint
  • status-success=mypy
  • status-success=test

Rule: automatic merge dependency updates (merge)

  • author~=(pyup-bot|dependabot)
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • -files~=^(!?.github/workflows/)
  • status-success=jslint
  • status-success=lint
  • status-success=mypy
  • status-success=test
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success = jslint
    • check-neutral = jslint
    • check-skipped = jslint
  • any of: [🛡 GitHub branch protection]
    • check-success = lint
    • check-neutral = lint
    • check-skipped = lint
  • any of: [🛡 GitHub branch protection]
    • check-success = mypy
    • check-neutral = mypy
    • check-skipped = mypy
  • any of: [🛡 GitHub branch protection]
    • check-success = test
    • check-neutral = test
    • check-skipped = test

Rule: automatic merge for master when CI passes and trusted comitter (queue)

  • author=@PennyDreadfulMTG/automerge
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base=master
  • status-success=jslint
  • status-success=lint
  • status-success=mypy
  • status-success=test
  • 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 = jslint
        • check-neutral = jslint
        • check-skipped = jslint
      • any of: [🛡 GitHub branch protection]
        • check-success = lint
        • check-neutral = lint
        • check-skipped = lint
      • any of: [🛡 GitHub branch protection]
        • check-success = mypy
        • check-neutral = mypy
        • check-skipped = mypy
      • any of: [🛡 GitHub branch protection]
        • check-success = test
        • check-neutral = test
        • check-skipped = test
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

View more details on Mergify