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

[8.13] Create delete-serverless-dir-in-backports.yml (backport #5300) #5307

Merged
merged 1 commit into from
Jun 5, 2024

Create delete-serverless-dir-in-backports.yml (#5300)

e06e7e8
Select commit
Loading
Failed to load commit list.
Merged

[8.13] Create delete-serverless-dir-in-backports.yml (backport #5300) #5307

Create delete-serverless-dir-in-backports.yml (#5300)
e06e7e8
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jun 5, 2024 in 3s

1 rule matches and 2 potential rules

⚠️ The pull request has been merged by @joepeeples

Rule: ask to resolve conflict (comment)

  • conflict

Rule: remove backport-skip label (label)

  • label~=^v\d

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

🚀  You can help us by becoming a sponsor!


20 not applicable rules

Rule: backport patches to 8.14 branch (backport)

  • base=main
  • label=v8.14.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.13 branch (backport)

  • base=main
  • label=v8.13.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.12 branch (backport)

  • base=main
  • label=v8.12.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.11 branch (backport)

  • base=main
  • label=v8.11.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.10 branch (backport)

  • base=main
  • label=v8.10.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.9 branch (backport)

  • base=main
  • label=v8.9.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.8 branch (backport)

  • base=main
  • label=v8.8.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.7 branch (backport)

  • base=main
  • label=v8.7.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.6 branch (backport)

  • base=main
  • label=v8.6.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.5 branch (backport)

  • base=main
  • label=v8.5.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.4 branch (backport)

  • base=main
  • label=v8.4.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.3 branch (backport)

  • base=main
  • label=v8.3.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.2 branch (backport)

  • base=main
  • label=v8.2.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.1 branch (backport)

  • base=main
  • label=v8.1.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 7.17 branch (backport)

  • base=main
  • label=v7.17.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.0 branch (backport)

  • base=main
  • label=v8.0.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 7.16 branch (backport)

  • base=main
  • label=v7.16.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 7.15 branch (backport)

  • base=main
  • label=v7.15.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 7.14 branch (backport)

  • base=main
  • label=v7.14.0
  • merged
  • merged [📌 backport requirement]

Rule: notify the backport policy (comment, label)

  • base=main
  • -label~=(^v\d|backport-skip)
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