Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Bump Khepri to v0.13.0 #10868

Merged
merged 1 commit into from
Mar 28, 2024

Bump Khepri to v0.13.0

b83efd4
Select commit
Loading
Failed to load commit list.
Merged

Bump Khepri to v0.13.0 #10868

Bump Khepri to v0.13.0
b83efd4
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Mar 28, 2024 in 1s

3 rules match and 3 potential rules

⚠️ The pull request has been merged by @the-mikedavis

✅ Rule: Add bazel label if a Bazel file is modified (label)

  • files~=\.(bazel|bzl)$

✅ Rule: Add make label if a Make file is modified (label)

  • files~=(Makefile|\.mk)$

✅ Rule: Automatically backport to v3.13.x based on label (backport)

  • base=main
  • label!=backport-v3.10.x
  • label!=backport-v3.11.x
  • label!=backport-v3.12.x
  • label=backport-v3.13.x
  • merged [📌 backport requirement]

Rule: Automatically backport to v3.13.x & v3.12.x based on label (backport)

  • label=backport-v3.12.x
  • base=main
  • label!=backport-v3.10.x
  • label!=backport-v3.11.x
  • label=backport-v3.13.x
  • merged [📌 backport requirement]

Rule: Automatically backport to v3.13.x, v3.12.x & v3.11.x based on labels (backport)

  • label=backport-v3.11.x
  • label=backport-v3.12.x
  • base=main
  • label!=backport-v3.10.x
  • label=backport-v3.13.x
  • merged [📌 backport requirement]

Rule: Automatically backport to v3.13.x, v3.12.x, v3.11.x & v3.10.x based on labels (backport)

  • label=backport-v3.10.x
  • label=backport-v3.11.x
  • label=backport-v3.12.x
  • base=main
  • label=backport-v3.13.x
  • merged [📌 backport requirement]
💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

6 not applicable rules

Rule: Automatically backport to v3.12.x based on label (backport)

  • base=v3.13.x
  • label=backport-v3.12.x
  • label!=backport-v3.10.x
  • label!=backport-v3.11.x
  • merged [📌 backport requirement]

Rule: Automatically backport to v3.12.x & v3.11.x based on labels (backport)

  • base=v3.13.x
  • label=backport-v3.11.x
  • label=backport-v3.12.x
  • label!=backport-v3.10.x
  • merged [📌 backport requirement]

Rule: Automatically backport to v3.12.x, v3.11.x & v3.10.x based on labels (backport)

  • base=v3.13.x
  • label=backport-v3.10.x
  • label=backport-v3.11.x
  • label=backport-v3.12.x
  • merged [📌 backport requirement]

Rule: Automatically backport to v3.11.x based on label (backport)

  • base=v3.12.x
  • label=backport-v3.11.x
  • label!=backport-v3.10.x
  • merged [📌 backport requirement]

Rule: Automatically backport to v3.11.x & v3.10.x based on labels (backport)

  • base=v3.12.x
  • label=backport-v3.10.x
  • label=backport-v3.11.x
  • merged [📌 backport requirement]

Rule: Automatically backport to v3.10.x based on label (backport)

  • base=v3.11.x
  • label=backport-v3.10.x
  • 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