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 client/v2 v2.0.0-beta3; fix broken client.toml usage (backport #3210) #3224

Merged
merged 1 commit into from
Jul 22, 2024

fix: use client/v2 v2.0.0-beta3; fix broken client.toml usage (#3210)

9792691
Select commit
Loading
Failed to load commit list.
Merged

fix: use client/v2 v2.0.0-beta3; fix broken client.toml usage (backport #3210) #3224

fix: use client/v2 v2.0.0-beta3; fix broken client.toml usage (#3210)
9792691
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 22, 2024 in 1s

1 rule matches

⚠️ The pull request has been merged by @MSalopek


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

🚀  You can help us by becoming a sponsor!


4 not applicable rules

Rule: Automatic merge on approval to the main branch (queue)

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

Rule: Automatic merge on approval to the main branch (merge)

  • -closed [📌 merge requirement]
  • base=main
  • label=A:automerge
  • #approved-reviews-by>=1
  • #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

Rule: Backport patches to the release/v18.1.x branch (backport)

  • base=main
  • label=A:backport/v18.1.x
  • merged [📌 backport requirement]

Rule: Backport patches to the release/v19.x branch (backport)

  • base=main
  • label=A:backport/v19.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