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

governance: let validator vote even if it doesn't have a self-bond (backport #3874) #3878

Merged
merged 1 commit into from
Oct 3, 2024

goveranance: let validator vote even if it doesn't have a self-bond

8ad0c48
Select commit
Loading
Failed to load commit list.
Merged

governance: let validator vote even if it doesn't have a self-bond (backport #3874) #3878

goveranance: let validator vote even if it doesn't have a self-bond
8ad0c48
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 3, 2024 in 0s

2 potential rules

⚠️ The pull request has been merged by @tzemanovic

‼️ 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/
‼️ 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: notify when a PR is removed from the queue (comment)

  • queue-dequeue-reason != none
  • queue-dequeue-reason != pr-merged

Rule: backport PR to 0.44.0 lane (backport)

  • label = backport-44
  • 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 to main or backport branch (queue)

  • -closed [📌 queue requirement]
  • any of:
    • base = "0.44.0"
    • base = main
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue backport-0.44-queue]
      • base = "0.44.0"
      • #approved-reviews-by >= 1
    • all of: [📌 queue conditions of queue main-queue]
      • base = main
      • #approved-reviews-by >= 1
  • #approved-reviews-by >= 1
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • label != "do-not-merge"
  • label = "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

View more details on Mergify