Skip to content

merge queue: checking main (8797535) and #1591 together - #1985

Draft
mergify[bot] wants to merge 43 commits into
mainfrom
mergify/merge-queue/31b949f8a7
Draft

merge queue: checking main (8797535) and #1591 together#1985
mergify[bot] wants to merge 43 commits into
mainfrom
mergify/merge-queue/31b949f8a7

Conversation

@mergify

@mergify mergify Bot commented Aug 5, 2026

Copy link
Copy Markdown

⏳ The pull request #1591 is queued for merge and currently being checked. ⏳

Branch main (8797535) and #1591 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #1591.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule main queue for merge:

  • any of [🛡 GitHub branch protection]:
    • check-neutral = all
    • check-skipped = all
    • check-success = all
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = pre-commit.ci - pr
    • check-neutral = pre-commit.ci - pr
    • check-skipped = pre-commit.ci - pr

Required conditions to stay in the queue:

---
checking_base_sha: 8797535e2ebcdecc022f1d9cf8be0d6c80887d3a
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1591
    scopes: []
scopes: []
...

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Thanks @mergify[bot] for opening this PR!

You can do multiple things directly here:
1 - Comment pre-commit.ci run to run pre-commit checks.
2 - Comment pre-commit.ci autofix to apply fixes.
3 - Add label autofix.ci to fix authorship & pre-commit for every commit made.
4 - Add label light-ci to only trigger a reduced & faster version of the CI (need the full one before merge).
5 - Add label trigger-ci to create an empty commit to trigger the CI.

Once the workflow completes a message will appear displaying informations related to the run.

Also the PR gets automatically reviewed by gemini, you can:
1 - Comment /gemini review to trigger a review
2 - Comment /gemini summary for a summary
3 - Tag it using @gemini-code-assist either in the PR or in review comments on files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants