Never stop coding. Free MIT AI gateway: one endpoint, 375 providers (150+ free), 1,400+ models Kimi, Claude, GPT, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. Quota-aware auto-fallback, RTK+Caveman compression saves 15-95% tokens, MCP/A2A, Desktop/PWA. Built by 900+ contributors
TypeScript a2aai-agentsai-gatewayanthropicclaudeclaude-codeclinecodexcopilotcursordeepseekfree-aigeminikimillm-gatewaymcpopenaiopenai-proxyqwentoken-saver
fix(ci): add the auto-enqueue pull_request_rule to the Mergify config (queue_conditions alone are eligibility-only) (#7179)
Diego Rodrigues de Sa e Souzafb24740b7344
diff --git a/.mergify.yml b/.mergify.ymlindex 131c6d71a9..88bc431369 100644--- a/.mergify.yml+++ b/.mergify.yml@@ -46,6 +46,18 @@ queue_rules:merge_method: squashpull_request_rules:+ # AUTO-ENQUEUE trigger — queue_conditions alone only define ELIGIBILITY in current+ # Mergify semantics (without this rule the PR sits at "use @Mergifyio queue",+ # observed live on PR #7175). The conditions mirror queue_conditions on purpose.+ - name: queue on owner-applied label+ conditions:+ - base~=^release/v\d+\.\d+\.\d+$+ - label=queue+ - -draft+ - -conflict+ actions:+ queue:+ name: release- name: clean up the queue label after mergeconditions:- merged