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

update WriteUpgradeTry to change flush status to FLUSHCOMPLETE if there are no packet commitments left #3964

Merged

assert on return arg

788184b
Select commit
Loading
Failed to load commit list.
Merged

update WriteUpgradeTry to change flush status to FLUSHCOMPLETE if there are no packet commitments left #3964

assert on return arg
788184b
Select commit
Loading
Failed to load commit list.
This check has been archived and is scheduled for deletion. Learn more about checks retention
Mergify / Summary succeeded Jun 28, 2023 in 2s

no rules match, no planned actions

⚠️ The pull request has been merged by @charleenfei


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

🚀  You can help us by becoming a sponsor!


10 not applicable rules

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

  • base=main
  • label=automerge
  • #approved-reviews-by>=1
  • -draft [:pushpin: queue requirement]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • any of: [:twisted_rightwards_arrows: routing conditions]
    • all of [:pushpin: routing conditions of queue default]
  • any of: [🛡 GitHub branch protection]
    • check-success=cleanup-runs
    • check-neutral=cleanup-runs
    • check-skipped=cleanup-runs
  • any of: [🛡 GitHub branch protection]
    • check-success=build (amd64)
    • check-neutral=build (amd64)
    • check-skipped=build (amd64)
  • any of: [🛡 GitHub branch protection]
    • check-success=build (arm)
    • check-neutral=build (arm)
    • check-skipped=build (arm)
  • any of: [🛡 GitHub branch protection]
    • check-success=build (arm64)
    • check-neutral=build (arm64)
    • check-skipped=build (arm64)
  • 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 v4.1.x branch (backport)

  • base=main
  • label=backport-to-v4.1.x
  • merged [:pushpin: backport requirement]

Rule: backport patches to v4.2.x branch (backport)

  • base=main
  • label=backport-to-v4.2.x
  • merged [:pushpin: backport requirement]

Rule: backport patches to v4.3.x branch (backport)

  • base=main
  • label=backport-to-v4.3.x
  • merged [:pushpin: backport requirement]

Rule: backport patches to v4.4.x branch (backport)

  • base=main
  • label=backport-to-v4.4.x
  • merged [:pushpin: backport requirement]

Rule: backport patches to v5.2.x branch (backport)

  • base=main
  • label=backport-to-v5.2.x
  • merged [:pushpin: backport requirement]

Rule: backport patches to v5.3.x branch (backport)

  • base=main
  • label=backport-to-v5.3.x
  • merged [:pushpin: backport requirement]

Rule: backport patches to v6.1.x branch (backport)

  • base=main
  • label=backport-to-v6.1.x
  • merged [:pushpin: backport requirement]

Rule: backport patches to v6.2.x branch (backport)

  • base=main
  • label=backport-to-v6.2.x
  • merged [:pushpin: backport requirement]

Rule: backport patches to v7.2.x branch (backport)

  • base=main
  • label=backport-to-v7.2.x
  • merged [:pushpin: 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