.mergify.yml

queue_rules:
  - name: default
    conditions:
      - check-success=fleet-ci/pr-merge
pull_request_rules:
  - name: self-assign PRs
    conditions:
      - -merged
      - -closed
      - "#assignee=0"
    actions:
      assign:
        add_users:
          - "{{ author }}"
  - name: ask to resolve conflict
    conditions:
      - -merged
      - -closed
      - conflict
      - -author=apmmachine
    actions:
        comment:
          message: |
            This pull request is now in conflicts. Could you fix it? 🙏
            To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/
            ```
            git fetch upstream
            git checkout -b {{head}} upstream/{{head}}
            git merge upstream/{{base}}
            git push upstream {{head}}
            ```
  - name: delete upstream branch after merging changes on .go-version or it's closed
    conditions:
      - or:
        - merged
        - closed
      - and:
        - label=automation
        - head~=^update-go-version
        - files~=^\.go-version$
    actions:
      delete_head_branch:
  - name: automatic approval for mergify pull requests with changes in bump-rules
    conditions:
      - author=mergify[bot]
      - check-success=fleet-ci/pr-merge
      - label=automation
      - files~=^\.mergify\.yml$
      - head~=^add-backport-next.*
    actions:
      review:
        type: APPROVE
        message: Automatically approving mergify
  - name: automatic squash and merge with success checks and the files matching the regex ^.mergify.yml is modified.
    conditions:
      - check-success=fleet-ci/pr-merge
      - label=automation
      - files~=^\.mergify\.yml$
      - head~=^add-backport-next.*
      - "#approved-reviews-by>=1"
    actions:
      queue:
        method: squash
        name: default
  - name: delete upstream branch with changes on ^.mergify.yml that has been merged or closed
    conditions:
      - or:
        - merged
        - closed
      - and:
        - label=automation
        - head~=^add-backport-next.*
        - files~=^\.mergify\.yml$
    actions:
      delete_head_branch:
  - name: notify the backport has not been merged yet
    conditions:
      - -merged
      - -closed
      - author=mergify[bot]
      - "#check-success>0"
      - schedule=Mon-Mon 06:00-10:00[Europe/Paris]
      - "#assignee>=1"
    actions:
      comment:
        message: |
          This pull request has not been merged yet. Could you please review and merge it @{{ assignee | join(', @') }}? 🙏
  - name: notify the backport policy
    conditions:
      - -label~=^backport
      - base=main
      - -merged
      - -closed
    actions:
      comment:
        message: |
          This pull request does not have a backport label.
          If this is a bug or security fix, could you label this PR @{{author}}? 🙏.
          For such, you'll need to label your PR with:
          * The upcoming major version of the Elastic Stack
          * The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

          To fixup this pull request, you need to add the backport labels for the needed
          branches, such as:
          * `backport-v8./d.0` is the label to automatically backport to the `8./d` branch. `/d` is the digit
  - name: backport patches to 8.5 branch
    conditions:
      - merged
      - label=backport-v8.5.0
    actions:
      backport:
        assignees:
          - "{{ author }}"
        branches:
          - "8.5"
        labels:
          - "backport"
        title: "[{{ destination_branch }}](backport #{{ number }}) {{ title }}"