WIP: Add asset inventory AWS CloudFront fetcher #2209
Closed
Mergify / Summary
succeeded
May 27, 2024 in 1s
17 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
-
-merged
Rule: notify the backport policy (comment, label)
-
-closed
-
-label~=^backport
-
-merged
-
base=main
Rule: remove-backport label (label)
-
-closed
-
label~=backport-v
-
-merged
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]
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
6 not applicable rules
Rule: close automated pull requests with bump updates if any conflict (close)
-
-closed
-
author=apmmachine
-
conflict
-
label=automation
-
-merged
Rule: delete upstream branch after merging changes on .go-version or it's closed (delete_head_branch)
- all of:
-
files~=^\.go-version$
-
head~=^update-go-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)
-
author=mergify[bot]
-
check-success=Cloudbeat-CI / Build (pull_request)
-
check-success=Cloudbeat-CI / Integration Tests (pull_request)
-
check-success=UnitTests / Unit Tests (pull_request)
-
files~=^\.mergify\.yml$
-
head~=^add-backport-next.*
-
label=automation
Rule: automatic squash and merge with success checks and the files matching the regex ^.mergify.yml is modified. (queue)
-
#approved-reviews-by>=1
-
-draft
[📌 queue requirement] -
check-success=Cloudbeat-CI / Build (pull_request)
-
check-success=Cloudbeat-CI / Integration Tests (pull_request)
-
check-success=UnitTests / Unit Tests (pull_request)
-
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 branch protection] -
branch-protection-review-decision=APPROVED
[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=CLA
-
check-neutral=CLA
-
check-skipped=CLA
-
- any of: [🛡 GitHub branch protection]
-
check-success=Package Cloudbeat (docker)
-
check-neutral=Package Cloudbeat (docker)
-
check-skipped=Package Cloudbeat (docker)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Package Cloudbeat (tar.gz)
-
check-neutral=Package Cloudbeat (tar.gz)
-
check-skipped=Package Cloudbeat (tar.gz)
-
- any of: [🛡 GitHub branch protection]
-
check-success=Manifest Tests
-
check-neutral=Manifest Tests
-
check-skipped=Manifest Tests
-
- any of: [🛡 GitHub branch protection]
-
check-success=Test Rego Policies
-
check-neutral=Test Rego Policies
-
check-skipped=Test Rego Policies
-
- any of: [🛡 GitHub branch protection]
-
check-success=Build docker images
-
check-neutral=Build docker images
-
check-skipped=Build docker images
-
- any of: [🛡 GitHub branch protection]
-
check-success=Lint
-
check-neutral=Lint
-
check-skipped=Lint
-
- any of: [🛡 GitHub branch protection]
-
check-success=Unit Test
-
check-neutral=Unit Test
-
check-skipped=Unit Test
-
- any of: [🛡 GitHub branch protection]
-
check-success=CNVM CI
-
check-neutral=CNVM CI
-
check-skipped=CNVM CI
-
- any of: [🛡 GitHub branch protection]
-
check-success=CIS Azure CI
-
check-neutral=CIS Azure CI
-
check-skipped=CIS Azure CI
-
- any of: [🛡 GitHub branch protection]
-
check-success=CIS AWS CI
-
check-neutral=CIS AWS CI
-
check-skipped=CIS AWS CI
-
- any of: [🛡 GitHub branch protection]
-
check-success=CIS GCP CI
-
check-neutral=CIS GCP CI
-
check-skipped=CIS GCP CI
-
-
- all of: [📌 queue conditions of queue
- 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 has not been merged yet (comment)
-
-closed
-
author=mergify[bot]
-
schedule=Mon-Mon 06:00-10:00[Europe/Paris]
-
#assignee>=1
-
#check-success>0
-
-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
Loading