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

fix: throw an error if incorrect ledger is used #374

Merged
merged 8 commits into from
Mar 13, 2024

Merge branch 'release/v0.46.x-celestia' into rp/error-for-incorrect-l…

23151ed
Select commit
Loading
Failed to load commit list.
Merged

fix: throw an error if incorrect ledger is used #374

Merge branch 'release/v0.46.x-celestia' into rp/error-for-incorrect-l…
23151ed
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Mar 13, 2024 in 1s

no rules match, no planned actions

⚠️ The pull request has been merged by @cmwaters

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

5 not applicable rules

Rule: automerge to main with label automerge and branch protection passing (queue)

  • base=main
  • label=A:automerge
  • #approved-reviews-by>1
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • 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]
      • any of: [🛡 GitHub branch protection]
        • check-success=golangci-lint
        • check-neutral=golangci-lint
        • check-skipped=golangci-lint
      • any of: [🛡 GitHub branch protection]
        • check-success=tests (00)
        • check-neutral=tests (00)
        • check-skipped=tests (00)
      • any of: [🛡 GitHub branch protection]
        • check-success=tests (01)
        • check-neutral=tests (01)
        • check-skipped=tests (01)
      • any of: [🛡 GitHub branch protection]
        • check-success=tests (02)
        • check-neutral=tests (02)
        • check-skipped=tests (02)
      • any of: [🛡 GitHub branch protection]
        • check-success=tests (03)
        • check-neutral=tests (03)
        • check-skipped=tests (03)

Rule: backport patches to v0.46.x branch (backport)

  • base=main
  • label=backport/0.46.x
  • merged [📌 backport requirement]

Rule: backport patches to v0.45.x branch (backport)

  • base=main
  • label=backport/0.45.x
  • merged [📌 backport requirement]

Rule: backport patches to v0.44.x branch (backport)

  • base=main
  • label=backport/0.44.x
  • merged [📌 backport requirement]

Rule: backport patches to v0.42.x branch (backport)

  • base=main
  • label=backport/0.42.x (Stargate)
  • merged [📌 backport requirement]
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