Fix bad error handling in api key auth #3935
Merged
Mergify / Summary
succeeded
Sep 20, 2024 in 2s
1 rule matches and 17 potential rules
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|backport-7.17)$
-
base=main
-
merged
-
merged
[📌 backport requirement]
Rule: automatic merge when CI passes and the file dev-tools/integration/.env is modified. (queue)
-
-closed
[📌 queue requirement] -
check-success=fleet-server/pr-merge
-
files~=^dev-tools/integration/.env$
-
label=automation
-
-conflict
[📌 queue requirement] -
-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] -
#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/fleet-server
-
check-neutral = buildkite/fleet-server
-
check-skipped = buildkite/fleet-server
-
-
- all of: [📌 queue conditions of queue
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|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]
Rule: notify the backport policy (comment)
-
-closed
-
-label~=^backport
-
-merged
-
base=main
Rule: add backport-8.x label for main only if no skipped or assigned already (comment, label)
-
-closed
-
-label~=^(backport-skip|backport-8.x)$
-
-merged
-
base=main
💖 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)
-
-closed
[📌 queue requirement] -
author=mergify[bot]
-
base~=^(7|8)\.
-
check-success=fleet-server/pr-merge
-
label=backport
-
-conflict
[📌 queue requirement] -
-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] -
#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/fleet-server
-
check-neutral = buildkite/fleet-server
-
check-skipped = buildkite/fleet-server
-
-
- all of: [📌 queue conditions of queue
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
Loading