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

Update pipeline.tests-staging.yaml #3706

Merged
merged 2 commits into from
Jul 10, 2024

Merge remote-tracking branch 'upstream/main' into fix-quality-gates

5c19c56
Select commit
Loading
Failed to load commit list.
Merged

Update pipeline.tests-staging.yaml #3706

Merge remote-tracking branch 'upstream/main' into fix-quality-gates
5c19c56
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 10, 2024 in 1s

16 potential rules

⚠️ The pull request has been merged by @juliaElastic

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

  • label=forwardport-main
  • merged
  • merged [📌 backport requirement]

Rule: ask to resolve conflict (comment)

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

Rule: backport patches to 7.17 branch (backport)

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

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
  • files~=^dev-tools/integration/.env$
  • label=automation
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 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: backport patches to 8.6 branch (backport)

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

Rule: backport patches to 8.7 branch (backport)

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

Rule: backport patches to 8.8 branch (backport)

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

Rule: backport patches to 8.9 branch (backport)

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

Rule: backport patches to 8.10 branch (backport)

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

Rule: backport patches to 8.11 branch (backport)

  • label=backport-v8.11.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.12 branch (backport)

  • label=backport-v8.12.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.13 branch (backport)

  • label=backport-v8.13.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.14 branch (backport)

  • label=backport-v8.14.0
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.15 branch (backport)

  • label=backport-v8.15.0
  • merged
  • merged [📌 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: close automated pull requests with bump updates if any conflict (close)

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

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

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

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

  • author=mergify[bot]
  • base~=^(7|8)\.
  • check-success=fleet-server/pr-merge
  • label=backport
  • -draft [📌 queue requirement]
  • check-success=CLA
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🔀 queue conditions]
    • all of: [📌 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]
  • base~=^(7|8)\.
  • check-success=fleet-server/pr-merge
  • label=backport
  • check-success=CLA

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

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