docs: Add post about Responses API in Llama Stack #5196
Merged
Mergify / Summary
succeeded
Mar 19, 2026 in 2s
3 potential rules
Rule: ping author on conflicts and add 'needs-rebase' label (comment, label)
-
-closed -
conflict -
-label~=stale
Rule: remove 'needs-rebase' label when conflict is resolved (label)
-
-closed -
-conflict
Rule: automatically update PRs that are 3+ commits behind main (update)
-
#commits-behind > 0[📌 update requirement] -
#commits-behind>=3 -
-closed -
-closed[📌 update requirement] -
-conflict -
-conflict[📌 update requirement] -
-draft -
base=main -
queue-position = -1[📌 update requirement]
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
3 not applicable rules
Rule: auto-approve dependabot github-deps PRs (review)
-
-closed -
author=dependabot[bot] -
title~=^chore\(github-deps\) -
-conflict -
-draft
Rule: auto-merge dependabot github-deps PRs (merge)
-
-closed -
-closed[📌 merge requirement] -
author=dependabot[bot] -
title~=^chore\(github-deps\) -
#approved-reviews-by >= 1[🛡 GitHub branch protection] -
#approved-reviews-by>=1 -
#changes-requested-reviews-by = 0[🛡 GitHub branch protection] -
#commits-behind = 0[🛡 GitHub branch protection] -
-conflict -
-conflict[📌 merge requirement] -
-draft -
-draft[📌 merge requirement] -
branch-protection-review-decision = APPROVED[🛡 GitHub branch protection] -
check-success=ci-status - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success = ci-status -
check-neutral = ci-status -
check-skipped = ci-status
-
Rule: auto-merge on stable release branches (merge)
-
-closed -
-closed[📌 merge requirement] -
base~=^release-[0-9]+\.[0-9]+\.x$ -
#approved-reviews-by >= 1[🛡 GitHub branch protection] -
#approved-reviews-by>=1 -
#changes-requested-reviews-by = 0[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0 -
#commits-behind = 0[🛡 GitHub branch protection] -
-conflict -
-conflict[📌 merge requirement] -
-draft -
-draft[📌 merge requirement] -
branch-protection-review-decision = APPROVED[🛡 GitHub branch protection] -
check-success=ci-status - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
- any of: [🛡 GitHub branch protection]
-
check-success = ci-status -
check-neutral = ci-status -
check-skipped = ci-status
-
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