Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

k8s-autodiscovery: notify in slack #3647

Merged
merged 2 commits into from
Sep 20, 2023

Update .github/workflows/k8s-autodiscovery-test.yml

3fc17bf
Select commit
Loading
Failed to load commit list.
Merged

k8s-autodiscovery: notify in slack #3647

Update .github/workflows/k8s-autodiscovery-test.yml
3fc17bf
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 20, 2023 in 2s

1 rule matches and 11 potential rules

⚠️ The pull request has been merged by @v1v

Rule: ask to resolve conflict (comment)

  • conflict

Rule: delete head branch after merge (delete_head_branch)

  • closed [:pushpin: delete_head_branch requirement]
  • merged

Rule: remove-backport label (label)

  • label~=backport-v

Rule: notify the backport policy (comment, label)

  • -label~=^backport
  • base=main

Rule: backport patches to 7.17 branch (backport)

  • label=backport-v7.17.0
  • base=main
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 8.3 branch (backport)

  • label=backport-v8.3.0
  • base=main
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 8.4 branch (backport)

  • label=backport-v8.4.0
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 8.5 branch (backport)

  • label=backport-v8.5.0
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 8.6 branch (backport)

  • label=backport-v8.6.0
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 8.7 branch (backport)

  • label=backport-v8.7.0
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 8.8 branch (backport)

  • label=backport-v8.8.0
  • merged
  • merged [:pushpin: backport requirement]

Rule: backport patches to 8.9 branch (backport)

  • label=backport-v8.9.0
  • merged
  • merged [:pushpin: backport requirement]

💖  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 squash and merge with success checks for those automated PRs created by the apmmachine. (queue)

  • -closed
  • -merged
  • author=apmmachine
  • head~=^updatecli.*
  • label=automation
  • -draft [:pushpin: queue requirement]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • any of: [:twisted_rightwards_arrows: queue conditions]
    • all of: [:pushpin: queue conditions of queue default]
      • any of: [🛡 GitHub branch protection]
        • check-success=CLA
        • check-neutral=CLA
        • check-skipped=CLA
      • any of: [🛡 GitHub branch protection]
        • check-success=Run Test
        • check-neutral=Run Test
        • check-skipped=Run Test
      • any of: [🛡 GitHub branch protection]
        • check-success=pre-commit
        • check-neutral=pre-commit
        • check-skipped=pre-commit

Rule: delete upstream branch after merging changes the automated PR or it's closed (delete_head_branch)

  • all of:
    • head~=^updatecli.*
    • label=automation
  • closed [:pushpin: delete_head_branch requirement]
  • any of:
    • closed
    • merged

Rule: notify the backport has not been merged yet (comment)

  • -closed
  • -merged
  • author=mergify[bot]
  • schedule=Mon-Mon 06:00-10:00[Europe/Paris]
  • #check-success>0
  • created-at<2 days ago

Rule: automatic close the automated PRs that have not been merged. (close)

  • -closed
  • -merged
  • author=apmmachine
  • created-at<3 days ago
  • head~=^updatecli.*
  • schedule=Mon-Fri 06:00-10:00[Europe/Paris]
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