Skip to content

feat: runtime env #712

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

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

fix: stabilize flaky ValidatorDetailsModal disabled button test

56cc134
Select commit
Loading
Failed to load commit list.
Open

feat: runtime env #712

fix: stabilize flaky ValidatorDetailsModal disabled button test
56cc134
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Feb 19, 2026 in 1s

3 potential rules

Rule: backport merged PRs on main to release/qa (backport)

  • merged
  • merged [📌 backport requirement]
  • base = main

Rule: backport merged main to testnet when labeled (backport)

  • label = promote:testnet
  • merged
  • merged [📌 backport requirement]
  • base = main

Rule: backport merged main to mainnet when labeled (backport)

  • label = promote:mainnet
  • merged
  • merged [📌 backport requirement]
  • base = main
3 not applicable rules

Rule: auto-merge backport into release/qa (queue)

  • author = mergify[bot]
  • base = release/qa
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • -conflict
      • check-success=build
  • -closed [📌 queue requirement]
  • -conflict
  • -conflict [📌 queue requirement]
  • -draft
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: auto-merge created backport into release/testnet (queue)

  • author = mergify[bot]
  • base = release/testnet
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • -conflict
      • check-success=build
  • -closed [📌 queue requirement]
  • -conflict
  • -conflict [📌 queue requirement]
  • -draft
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: auto-merge created backport into release/mainnet (queue)

  • author = mergify[bot]
  • base = release/mainnet
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • -conflict
      • check-success=build
  • -closed [📌 queue requirement]
  • -conflict
  • -conflict [📌 queue requirement]
  • -draft
  • -draft [📌 queue requirement]
  • 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