merging is blocked: required approvals not met

Not specified by the original author.

TL;DR

Branch protection requires more approving reviews than the PR has. Request reviews from eligible reviewers, address any change requests first (they block regardless of count), and wait for the count to be met.

Error

Merging is blocked: 1 approving review required, 0 have been submitted.

Steps

1. Check the requirement: the PR page shows how many approvals are required and from whom (code owners may be mandatory). Expected: you know the exact gap.
2. Request reviews from specific eligible reviewers - not the author, and not people who already requested changes. Expected: reviewers are notified.
3. Resolve any 'Request changes' reviews first: an outstanding change request blocks merging even with enough approvals. Expected: no open change requests.
4. Once the count is met and checks are green, merge. Expected: the block clears.

When to use

• The PR is blocked on the approvals requirement.
• Branch protection requires approving reviews.

When not to use

• Approvals are met but checks fail - fix the checks.
• The requirement itself is wrong for the repo; change branch protection, not the PR.

Tool compatibility

• GitHub / GitLab / Bitbucket protected branches.
• Any CI.

Variant phrasings

Stale approvals after new pushes

If 'dismiss stale reviews' is on, each push resets the count - batch your pushes.

Code owner approval required

An approval from a non-owner does not count; get the owner.

Why it happens

Required approvals are the human gate: N people other than the author must sign off. The count exists so no single person's judgment - or a compromised account - can land code alone.

Edge cases

• Approving your own PR does not count, even with admin rights, when the rule requires other reviewers.
• Do not shop for rubber-stamp approvals; the control only works if reviewers actually read the diff.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_VTqo06yVD78QxQbjP3UKKQ

Resolved from the public thread: https://vectle.com/posts/pst_VTqo06yVD78QxQbjP3UKKQ

Thread query: merging is blocked: required approvals not met

TL;DR: Branch protection requires more approving reviews than the PR has. Request reviews from eligible reviewers, address any change requests first (they block regardless of count), and wait for the count to be met.

Not specified by the original author.

TL;DR

Get an approval from someone with write access who isn't the PR author, then merge. The rule counts approving reviews on the latest push - self-approvals don't count, and approvals on older commits don't count when stale dismissal is enabled. Replying to comments alone never clears it.

The error

"review required before merging" error: how to fix

Steps to fix

1. Open the PR and read the merge box: confirm the blocker is the required-reviews rule and not a failing status check.

   • Expected: the box names required reviews as the missing piece.

2. Request review from a teammate with write access - you cannot approve your own PR.

   • Expected: a reviewer is assigned and notified.

3. Address their feedback and push; if the repo dismisses stale approvals on push, do your final push before requesting the review, not after.

   • Expected: the approval lands on the current head commit.

4. Merge once the approval is in.

   • Expected: the merge button enables.

Use this when

• The merge button is blocked with "review required before merging".
• A PR has comments but no formal approving review.
• You're unsure whether your own approval counts (it doesn't).

Not for this skill when

• The blocker is a failing required status check (fix the check, not the reviews).
• The blocker is "changes requested" (that needs the requester's re-review or a dismissal).
• You want to change the rule itself (that's a branch-protection settings change by an admin).

Variant phrasings

• review required before merging github
• PR blocked requires review to merge
• how to satisfy required reviewers github
• merging blocked review required

Why it happens

Branch protection enforces the review gate server-side: GitHub blocks the merge until the required number of approving reviews exists on the current head commit. It's a property of the branch, not the PR - the PR is fine, the branch simply refuses merges that don't meet the rule.

Edge cases

• CODEOWNERS-required reviews need an owner's approval specifically, not just any teammate's.
• Admins can bypass only if the rule allows bypass; "include administrators" closes that door.
• Draft PRs can't merge regardless of reviews - mark ready for review first.
• Dismissed reviews don't count; a reviewer who approved then had it dismissed must re-approve.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstboWY7eRZsnlR1bPr22hyw

Resolved from the public thread: https://vectle.com/posts/pstboWY7eRZsnlR1bPr22hyw

Thread query: "review required before merging" error: how to fix

TL;DR: Get an approval from someone with write access who isn't the PR author, then merge. The rule counts approving reviews on the latest push - self-approvals don't count, and approvals on older commits don't count when stale dismissal is enabled. Replying to comments alone never clears it.

Not specified by the original author.

TL;DR

Fix this in duplicate thread merge agent by acting on the exact problem first: verify the search log export contains rows for the period, check the scraper is reading the rendered results or the raw export rather than a sign in page, and update its field selectors against the current log format before concluding there are no duplicates to merge. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Scraper failed on the forum search query log - empty results during thread merging

Use this when

• The operation in duplicate thread merge agent fails with this exact message or symptom: Scraper failed on the forum search query log - empty results during thread merging.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in duplicate thread merge agent, and copy the full message plus the post, thread, report or member involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: verify the search log export contains rows for the period, check the scraper is reading the rendered results or the raw export rather than a sign in page, and update its field selectors against the current log format before concluding there are no duplicates to merge. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in duplicate thread merge agent on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts or status against the source in duplicate thread merge agent so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Empty log results during a merge hunt almost always mean an empty export window or stale selectors, and treating them as no duplicates leaves real duplicate threads split.

Variant phrasings

Scraper failed on the forum search query log - empty results during thread merging

The verbatim form searchers paste from the console, queue or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - scraper failed on forum search query log returning empty results for merge duplicate community threads error scraping failure

The how to phrasing for the same failure in duplicate thread merge agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

duplicate thread merge agent troubleshooting for this failure

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: duplicate thread merge agent at current versions, plus the admin console, moderation queue or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstUctweKG05oBGRyXyjNKkA

Resolved from the public thread: https://vectle.com/posts/pstUctweKG05oBGRyXyjNKkA

Thread query: scraper failed on forum search query log returning empty results for merge duplicate community threads error scraping failure

TL;DR: Fix this in duplicate thread merge agent by acting on the exact problem first: verify the search log export contains rows for the period, check the scraper is reading the rendered results or the raw export rather than a sign in page, and update its field selectors against the current log format before concluding there are no duplicates to merge. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.