mail/.mergify.yml at develop · frappe/mail · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
pull_request_rules:
  - name: Explain backport command on merged develop PRs
    conditions:
      - merged
      - base=develop
    actions:
      comment:
        message: |
          Backport this PR with Mergify by adding one of these comments:
          - `@Mergifyio backport v0`
          - `@Mergifyio backport v1`

          You can run both commands on the same PR when the fix must be backported to both release lines.

  - name: backport to v0
    conditions:
      - merged
      - base=develop
      - label="backport v0"
    actions:
      backport:
        branches:
          - v0
        assignees:
          - "{{ author }}"

  - name: backport to v1
    conditions:
      - merged
      - base=develop
      - label="backport v1"
    actions:
      backport:
        branches:
          - v1
        assignees:
          - "{{ author }}"

commands_restrictions:
  # By default Mergify only lets users with write access run `@Mergifyio backport`, so a PR
  # author commenting the backport command on their own merged PR is silently ignored. Allow the
  # author to backport their own PR in addition to maintainers.
  backport:
    conditions:
      - or:
          - sender-permission>=write
          - sender={{ author }}