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

feat!: migrate to distribute previously allocated rewards, and distribute unaccounted denoms #3361

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Merge branch 'main' into insumity/add-v21-upgrade

1626e11
Select commit
Loading
Failed to load commit list.
Open

feat!: migrate to distribute previously allocated rewards, and distribute unaccounted denoms #3361

Merge branch 'main' into insumity/add-v21-upgrade
1626e11
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 2, 2024 in 6s

4 potential rules

Rule: Automatic merge on approval to the main branch (merge)

  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #approved-reviews-by>=1
  • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
  • label=A:automerge
  • any of: [🛡 GitHub branch protection]
    • check-neutral = golangci-lint
    • check-skipped = golangci-lint
    • check-success = golangci-lint
  • any of: [🛡 GitHub branch protection]
    • check-neutral = test-e2e
    • check-skipped = test-e2e
    • check-success = test-e2e
  • any of: [🛡 GitHub branch protection]
    • check-neutral = tests
    • check-skipped = tests
    • check-success = tests
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • base=main
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Automatic merge on approval to the main branch (queue)

  • #approved-reviews-by>=1
  • label=A:automerge
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
      • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-neutral = golangci-lint
        • check-skipped = golangci-lint
        • check-success = golangci-lint
      • any of: [🛡 GitHub branch protection]
        • check-neutral = test-e2e
        • check-skipped = test-e2e
        • check-success = test-e2e
      • any of: [🛡 GitHub branch protection]
        • check-neutral = tests
        • check-skipped = tests
        • check-success = tests
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • base=main
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Backport patches to the release/v21.x branch (backport)

  • label=A:backport/v21.x
  • merged [📌 backport requirement]
  • base=main

Rule: Backport patches to the release/v20.x branch (backport)

  • label=A:backport/v20.x
  • merged [📌 backport requirement]
  • base=main

💖  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