Skip to content

prohibit adding nonce account to address lookup table #659

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

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

reverted changes in converInstruction function

65802ca
Select commit
Loading
Failed to load commit list.
Open

prohibit adding nonce account to address lookup table #659

reverted changes in converInstruction function
65802ca
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 17, 2025 in 0s

1 faulty rule and 2 potential rules

Rule: Add community label to outside contributions (label)

  • author≠@core-contributors ⚠️ Team @core-contributors does not exist
  • author≠@spl-maintainers ⚠️ Team @spl-maintainers does not exist
  • author≠@spl-triage ⚠️ Team @spl-triage does not exist
  • author≠@spl-write ⚠️ Team @spl-write does not exist
  • author≠dependabot[bot]
  • author≠github-actions[bot]
  • author≠mergify[bot]

Rule: Automatic merge (squash) on CI success (queue)

  • all of:
    • label=automerge
    • status-success=all-web3-checks
    • label!=no-automerge
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: Remove automerge label on CI failure (comment, label)

  • #status-failure!=0
  • label=automerge

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