fix(source-control): pull-request merge must confirm the PR entered the merge queue
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start with plugins/source-control/skills/pull-request/reference/merge.md and trace the merge phase’s gh pr merge flow. Check how it reads isInMergeQueue and invokes GitHub GraphQL; acceptance is met when a merge run ends with the PR queued or merged, or reports GitHub’s enqueue error verbatim.
Written by the indexing model from the issue text.
Description
Observed 2026-10-07: gh pr merge <n> --squash on a merge-queue branch prints "The merge strategy for main is set by the merge queue". Sometimes the PR still does not enter the queue: #6481 sat CLEAN, with auto-merge armed and isInMergeQueue false, until it was queued directly with the GraphQL enqueuePullRequest mutation. #6426 needed the same check.
GitHub's docs say a PR joins the queue through the merge button or auto-merge (https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue). The merge phase (plugins/source-control/skills/pull-request/reference/merge.md) should:
- after
gh pr merge, readisInMergeQueue; - when the PR is CLEAN and not queued, run
enqueuePullRequest; - report the enqueue error verbatim. For example, "A conversation must be resolved" names the blocker.
Acceptance: a merge run either ends with the PR queued or merged, or names the blocker GitHub returned.
- Dominant language
- Shell
- Stars
- 22
- Forks
- 2
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 833
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from melodic-software/claude-code-plugins
-
good first issue needs-triage priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#6631 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melodic-software/claude-code-plugins#6547 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melodic-software/claude-code-plugins#6535 ·
Maintainers usually reply within 1 day
-
test_comment_census.py: SccArgv flag-shaped-filename test errors on Windows (#!/bin/sh scc shim)Opengood first issue needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#6532 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#6390 · 1 comment ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws-samples/appmod-blueprints#972 ·
Maintainers usually reply within 1 day
-
[Bug]: remote-ls --updates reports up-to-date OCI refs because it ignores deployed Alt-idPossibly taken @Joao-kouznetz claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
status:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days