zscaler_zia: add strict field template mode for tcp and http_endpoint input data streams#13904
Merged
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Mergify / Summary
succeeded
May 25, 2025 in 1s
no rules match, no planned actions
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
2 not applicable rules
Rule: automatic merge of bot 🤖 (queue)
-
-closed[📌 queue requirement] -
author~=^dependabot(|-preview)\[bot\]$ -
check-success=integrations/pr-merge -
-conflict[📌 queue requirement] -
-draft[📌 queue requirement] -
base=main -
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] -
#approved-reviews-by >= 1[🛡 GitHub repository ruleset rule] -
#approved-reviews-by >= 1[🛡 GitHub repository ruleset rule] -
#changes-requested-reviews-by = 0[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0[🛡 GitHub repository ruleset rule] -
#changes-requested-reviews-by = 0[🛡 GitHub repository ruleset rule] -
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/integrations -
check-neutral = buildkite/integrations -
check-skipped = buildkite/integrations
-
- any of: [🛡 GitHub branch protection]
-
check-success = Check for blocked path changes -
check-neutral = Check for blocked path changes -
check-skipped = Check for blocked path changes
-
-
- all of: [📌 queue conditions of queue
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
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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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
Loading