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

GET /api/overview: format cluster and node tag lists as maps (backport #12797) #12798

Merged
merged 1 commit into from
Nov 25, 2024

GET /api/overview: format cluster and node tag lists as maps

e3e8554
Select commit
Loading
Failed to load commit list.
Merged

GET /api/overview: format cluster and node tag lists as maps (backport #12797) #12798

GET /api/overview: format cluster and node tag lists as maps
e3e8554
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 25, 2024 in 0s

3 potential rules

⚠️ The pull request has been merged by @michaelklishin

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)

  • label=backport-v3.13.x
  • base=v4.0.x
  • label!=backport-v3.12.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!


3 not applicable rules

Rule: Automatically backport to v4.0.x based on label (backport)

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

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

  • base=main
  • label=backport-v3.13.x
  • label=backport-v4.0.x
  • merged [📌 backport requirement]

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

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