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

[8.13](backport #39777) Add a note when using expand_event_list_from_field, content_type is required to set to application/json #39903

Closed
wants to merge 1 commit into from

Add a note when using `expand_event_list_from_field`, `content_type` …

2158ace
Select commit
Loading
Failed to load commit list.
Closed

[8.13](backport #39777) Add a note when using expand_event_list_from_field, content_type is required to set to application/json #39903

Add a note when using `expand_event_list_from_field`, `content_type` …
2158ace
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 16, 2024 in 2s

1 rule matches and 20 potential rules

Rule: self-assign PRs (assign)

  • #assignee=0
  • -closed
  • -merged

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

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

Rule: ask to resolve conflict (comment)

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

Rule: automatic squash and merge with success checks and the files matching the regex ^testing/environments/snapshot* are modified. (queue)

  • #approved-reviews-by>=1
  • -closed [📌 queue requirement]
  • check-success=buildkite/beats
  • files~=^testing/environments/snapshot.*\.yml$
  • label=automation
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
      • any of: [🛡 GitHub branch protection]
        • check-neutral = buildkite/beats
        • check-skipped = buildkite/beats
        • check-success = buildkite/beats
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
      • any of: [🛡 GitHub branch protection]
        • check-success = CLA
        • check-neutral = CLA
        • check-skipped = CLA
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

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

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

Rule: backport patches to 7.17 branch (backport)

  • label~=^(backport-v7.17.0|backport-7.17)$
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.3 branch (backport)

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

Rule: backport patches to 8.4 branch (backport)

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

Rule: backport patches to 8.5 branch (backport)

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

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|backport-8.15)$
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 8.x branch (backport)

  • label~=^(backport-v8.x|backport-8.x)$
  • 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!


9 not applicable rules

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

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

Rule: automatic approval for automated pull requests with bump updates (review)

  • author=apmmachine
  • check-success=buildkite/beats
  • files~=^testing/environments/snapshot.*\.yml$
  • label=automation

Rule: delete upstream branch after merging changes on testing/environments/snapshot* or it's closed (delete_head_branch)

  • all of:
    • files~=^testing/environments/snapshot.*\.yml$
    • head~=^updatecli_bump-elastic-stack
    • label=automation
  • closed [📌 delete_head_branch requirement]
  • any of:
    • closed
    • merged

Rule: delete upstream branch after merging changes on .go-version or it's closed (delete_head_branch)

  • all of:
    • files~=^\.go-version$
    • head~=^updatecli_bump-golang-version
    • label=automation
  • closed [📌 delete_head_branch requirement]
  • any of:
    • closed
    • merged

Rule: automatic approval for mergify pull requests with changes in bump-rules (review)

  • check-success=buildkite/beats
  • files~=^\.mergify\.yml$
  • head~=^add-backport-next.*
  • label=automation
  • author=mergify[bot]

Rule: automatic squash and merge with success checks and the files matching the regex ^.mergify.yml is modified. (queue)

  • #approved-reviews-by>=1
  • -closed [📌 queue requirement]
  • check-success=buildkite/beats
  • files~=^\.mergify\.yml$
  • head~=^add-backport-next.*
  • label=automation
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
      • any of: [🛡 GitHub branch protection]
        • check-neutral = buildkite/beats
        • check-skipped = buildkite/beats
        • check-success = buildkite/beats
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
      • any of: [🛡 GitHub branch protection]
        • check-success = CLA
        • check-neutral = CLA
        • check-skipped = CLA
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: delete upstream branch with changes on ^.mergify.yml that has been merged or closed (delete_head_branch)

  • all of:
    • files~=^\.mergify\.yml$
    • head~=^add-backport-next.*
    • label=automation
  • closed [📌 delete_head_branch requirement]
  • any of:
    • closed
    • merged

Rule: notify the backport policy (comment)

  • -closed
  • -label~=^backport
  • base=main
  • -merged

Rule: add backport-8.x label for main only if no skipped or assigned already (comment, label)

  • -closed
  • base=main
  • -label~=^(backport-skip|backport-8.x)$
  • -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