Enter Merge Queue FAQs

Question 1

Does it modify the PR description?

Accepted Answer

Yes, it keeps the PR body updated with a standardized summary of changes, testing results, and associated issue links while ensuring proper agent identification.

Question 2

Does it support high-priority PRs?

Accepted Answer

Yes, the workflow includes logic to yield to other high-priority PRs unless the current PR is also flagged as high-priority, ensuring critical updates are not blocked.

Question 3

How does the skill handle merge conflicts during a rebase?

Accepted Answer

The skill attempts an automatic resolution by preferring upstream changes for conflicting files. If conflicts persist after this attempt, it will abort the rebase and notify the user for manual intervention.

Question 4

Can it interact with Gemini code reviews?

Accepted Answer

Yes, the skill is specifically designed to poll for Gemini review comments, address the feedback by creating new commits, and reply to threads with commit hashes to confirm resolutions.

Question 5

What is adaptive polling and jitter?

Accepted Answer

The skill uses variable wait times based on how long CI has been running, combined with a ±20% randomization (jitter) to avoid hitting API rate limits and to mimic human-like monitoring patterns.

Enter Merge Queue

Key Features

Use Cases

Enter Merge Queue

Key Features

Use Cases