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

chore!: make the row proof range end exclusive #1376

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

Merge branch 'main' into conistent-rnage

83841be
Select commit
Loading
Failed to load commit list.
Open

chore!: make the row proof range end exclusive #1376

Merge branch 'main' into conistent-rnage
83841be
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 29, 2024 in 0s

2 potential rules

‼️ Action Required ‼️

The configuration uses the deprecated commit_message_template attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
A brownout is planned on August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

‼️ Action Required ‼️

The configuration uses the deprecated merge_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
A brownout is planned on August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

### Rule: Backport to v0.34.x-celestia (backport)
  • label=S:backport-to-v0.34.x
  • merged
  • merged [📌 backport requirement]
  • base=main

Rule: Backport to main (backport)

  • label=S:backport-to-main
  • merged
  • 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: Automerge to v0.34.x-celestia (queue)

  • base=v0.34.x-celestia
  • label=S:automerge
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=2 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=e2e-test
        • check-neutral=e2e-test
        • check-skipped=e2e-test
      • 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)
  • -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