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

[updatecli] update elastic stack version for testing 7.17.16-641039af-SNAPSHOT #3112

Merged
merged 2 commits into from
Nov 20, 2023

chore: Update snapshot.yml

07e419c
Select commit
Loading
Failed to load commit list.
Merged

[updatecli] update elastic stack version for testing 7.17.16-641039af-SNAPSHOT #3112

chore: Update snapshot.yml
07e419c
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 20, 2023 in 3s

1 rule matches and 11 potential rules

⚠️ The pull request has been merged by @jlind23

Rule: forward-port patches to main branch (backport)

  • label=forwardport-main
  • merged
  • merged [:pushpin: backport requirement]

Rule: close automated pull requests with bump updates if any conflict (close)

  • -closed
  • -merged
  • conflict
  • author=apmmachine
  • label=automation

Rule: remove backport-skip label (label)

  • label~=backport-v

Rule: automatic merge when CI passes and the file dev-tools/integration/.env is modified. (queue)

  • check-success=fleet-server/pr-merge
  • -draft [:pushpin: queue requirement]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • files~=^dev-tools/integration/.env$
  • label=automation
  • any of: [:twisted_rightwards_arrows: queue conditions]
    • all of: [:pushpin: queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=CLA
        • check-neutral=CLA
        • check-skipped=CLA
      • any of: [🛡 GitHub branch protection]
        • check-success=buildkite/fleet-server
        • check-neutral=buildkite/fleet-server
        • check-skipped=buildkite/fleet-server

Rule: automatic merge when CI passes and the file dev-tools/integration/.env is modified. (review)

  • check-success=fleet-server/pr-merge
  • files~=^dev-tools/integration/.env$
  • label=automation

Rule: delete upstream branch with changes on dev-tools/integration/.env or .go-version after merging/closing it (delete_head_branch)

  • closed [:pushpin: delete_head_branch requirement]
  • all of:
    • files~=^(dev-tools/integration/.env|.go-version)$
    • head~=^updatecli.*
    • label=automation
  • any of:
    • closed
    • merged

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]

Rule: backport patches to 8.10 branch (backport)

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

Rule: backport patches to 8.11 branch (backport)

  • label=backport-v8.11.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!


5 not applicable rules

Rule: ask to resolve conflict (comment)

  • -author=apmmachine
  • -closed
  • -merged
  • conflict

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

  • #assignee>=1
  • -closed
  • -merged
  • author=mergify[bot]
  • schedule=Mon-Mon 06:00-10:00[Europe/Paris]
  • #check-success>0

Rule: automatic merge for 7. or 8. branches when CI passes (queue)

  • author=mergify[bot]
  • check-success=fleet-server/pr-merge
  • label=backport
  • -draft [:pushpin: queue requirement]
  • -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
  • base~=^(7|8)\.
  • check-success=CLA
  • any of: [:twisted_rightwards_arrows: queue conditions]
    • all of: [:pushpin: queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
      • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-success=CLA
        • check-neutral=CLA
        • check-skipped=CLA
      • any of: [🛡 GitHub branch protection]
        • check-success=buildkite/fleet-server
        • check-neutral=buildkite/fleet-server
        • check-skipped=buildkite/fleet-server

Rule: automatic merge for 7. or 8. branches when CI passes (review)

  • author=mergify[bot]
  • check-success=fleet-server/pr-merge
  • label=backport
  • base~=^(7|8)\.
  • check-success=CLA

Rule: backport patches to 7.17 branch (backport)

  • base=main
  • label=backport-v7.17.0
  • merged
  • merged [:pushpin: backport requirement]
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