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

build(deps): bump actions/checkout from 4.1.7 to 4.2.0 #734

Closed

build(deps): bump actions/checkout from 4.1.7 to 4.2.0

fd326d4
Select commit
Loading
Failed to load commit list.
Closed

build(deps): bump actions/checkout from 4.1.7 to 4.2.0 #734

build(deps): bump actions/checkout from 4.1.7 to 4.2.0
fd326d4
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 8, 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.
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

‼️ Action Required ‼️

The configuration uses the deprecated allow_checks_interruption attribute in the queue_rules section. This option must now be set at the top level of the configuration file in the priority_rules section.
A brownout is planned on November 11th, 2024.
This option will be removed on December 11th, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#priority-rules
‼️ Action Required ‼️
**The configuration uses the deprecated speculative_checks attribute in the queue_rules section. It has been replaced in favor of max_parallel_checks in the merge_queue section of the configuration.
For more information: https://docs.mergify.com/merge-queue/speculative-checks/

Rule: main queue triggered when CI passes with 1 review (queue)

  • -closed [📌 queue requirement]
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue main]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • -conflict [📌 queue requirement]
  • -draft
  • -draft [📌 queue requirement]
  • base=main
  • label!=do-not-merge
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

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