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

fix: use UTC time for packet timeout error #4467

Closed
wants to merge 1 commit into from

fix: use UTC time for packet timeout error

7c97a9a
Select commit
Loading
Failed to load commit list.
Closed

fix: use UTC time for packet timeout error #4467

fix: use UTC time for packet timeout error
7c97a9a
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Aug 26, 2023 in 1s

no rules match, no planned actions


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

🚀  You can help us by becoming a sponsor!


9 not applicable rules

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

  • #approved-reviews-by>=1
  • base=main
  • label=automerge
  • any of: [:twisted_rightwards_arrows: queue conditions]
    • all of: [:pushpin: queue conditions of queue default]
      • #approved-reviews-by>=2 [🛡 GitHub branch protection]
      • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • 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=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 [:pushpin: queue requirement]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]

Rule: backport patches to v1.0.x capability branch (backport)

  • base=main
  • label=backport-capability-to-v1.0.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]

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

  • base=main
  • label=backport-to-v7.3.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