瀏覽代碼

Update mergify config for v3.1 backport label (#8814)

Will Hickey 3 周之前
父節點
當前提交
b210780a70
共有 1 個文件被更改,包括 16 次插入16 次删除
  1. 16 16
      .mergify.yml

+ 16 - 16
.mergify.yml

@@ -104,9 +104,9 @@ pull_request_rules:
           - automerge
           - automerge
       comment:
       comment:
         message: automerge label removed due to a CI failure
         message: automerge label removed due to a CI failure
-  - name: v2.3 feature-gate backport
+  - name: v3.0 feature-gate backport
     conditions:
     conditions:
-      - label=v2.3
+      - label=v3.0
       - label=feature-gate
       - label=feature-gate
     actions:
     actions:
       backport:
       backport:
@@ -117,10 +117,10 @@ pull_request_rules:
         labels:
         labels:
           - feature-gate
           - feature-gate
         branches:
         branches:
-          - v2.3
-  - name: v2.3 non-feature-gate backport
+          - v3.0
+  - name: v3.0 non-feature-gate backport
     conditions:
     conditions:
-      - label=v2.3
+      - label=v3.0
       - label!=feature-gate
       - label!=feature-gate
     actions:
     actions:
       backport:
       backport:
@@ -128,10 +128,10 @@ pull_request_rules:
         title: "{{ destination_branch }}: {{ title }} (backport of #{{ number }})"
         title: "{{ destination_branch }}: {{ title }} (backport of #{{ number }})"
         ignore_conflicts: true
         ignore_conflicts: true
         branches:
         branches:
-          - v2.3
-  - name: v2.3 backport warning comment
+          - v3.0
+  - name: v3.0 backport warning comment
     conditions:
     conditions:
-      - label=v2.3
+      - label=v3.0
     actions:
     actions:
       comment:
       comment:
         message: >
         message: >
@@ -142,9 +142,9 @@ pull_request_rules:
           refactoring, plumbing, cleanup, etc that are not strictly
           refactoring, plumbing, cleanup, etc that are not strictly
           necessary to achieve the goal. Any of the latter should go only
           necessary to achieve the goal. Any of the latter should go only
           into master and ride the normal stabilization schedule.
           into master and ride the normal stabilization schedule.
-  - name: v3.0 feature-gate backport
+  - name: v3.1 feature-gate backport
     conditions:
     conditions:
-      - label=v3.0
+      - label=v3.1
       - label=feature-gate
       - label=feature-gate
     actions:
     actions:
       backport:
       backport:
@@ -154,10 +154,10 @@ pull_request_rules:
         labels:
         labels:
           - feature-gate
           - feature-gate
         branches:
         branches:
-          - v3.0
-  - name: v3.0 non-feature-gate backport
+          - v3.1
+  - name: v3.1 non-feature-gate backport
     conditions:
     conditions:
-      - label=v3.0
+      - label=v3.1
       - label!=feature-gate
       - label!=feature-gate
     actions:
     actions:
       backport:
       backport:
@@ -165,10 +165,10 @@ pull_request_rules:
         title: "{{ destination_branch }}: {{ title }} (backport of #{{ number }})"
         title: "{{ destination_branch }}: {{ title }} (backport of #{{ number }})"
         ignore_conflicts: true
         ignore_conflicts: true
         branches:
         branches:
-          - v3.0
-  - name: v3.0 backport warning comment
+          - v3.1
+  - name: v3.1 backport warning comment
     conditions:
     conditions:
-      - label=v3.0
+      - label=v3.1
     actions:
     actions:
       comment:
       comment:
         message: >
         message: >