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

net/probes: Expect vector<byte> from cert_info #18287

Merged
merged 1 commit into from
May 14, 2024

net/probes: Expect vector<byte> from cert_info

ba62518
Select commit
Failed to load commit list.
Merged

net/probes: Expect vector<byte> from cert_info #18287

net/probes: Expect vector<byte> from cert_info
ba62518
Select commit
Failed to load commit list.
Mergify / Summary succeeded May 14, 2024 in 1s

1 potential rule

⚠️ The pull request has been merged by @oleiman

Rule: enqueue on label (queue)

  • label=merge-queue
  • -draft [📌 queue requirement]
  • base=dev
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue dev]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]

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