Skip to main content

Review Existing Open Merge Requests

Backfill exists so you do not need to wait for the next push or the next MR after connecting a repository. Buzzbin can review a selection of currently open MRs so you get feedback on your team's real code from day one.

Why it matters​

  • you reach a real product outcome faster
  • you evaluate Buzzbin on your own active code
  • there is no need to wait for the next push or the next MR

How the flow works​

  1. After a successful repository connection, Buzzbin finds eligible open MRs.
  2. A small set of suitable MRs is pre-selected.
  3. You adjust the selection and start the review run.
  4. Each selected MR goes through the same standard review pipeline, and the result is posted directly to that MR on GitLab, exactly like a normal review.
  5. You can follow the progress and outcome of each run on the Review Jobs page.

Which MRs are eligible​

In general, backfill focuses on MRs that are:

  • open
  • not draft
  • not stale
  • not already reviewed by Buzzbin

Ineligible MRs are usually shown with a reason such as draft, stale, or already reviewed.

Important constraints​

  • the number of selectable MRs is capped
  • Buzzbin does not enqueue every open MR automatically
  • each selected MR consumes credit the same way a normal review would
note

Backfill does not replace normal webhook-driven review. It is mainly an onboarding and controlled catch-up flow for current open MRs.

When to use it​

Backfill is the right tool when:

  • you just connected a repository
  • you want to evaluate review quality without waiting for the next push or MR
  • you want a quick pass over a handful of in-flight MRs

If you skip backfill​

That is fine. Buzzbin will continue working on future GitLab events only: new MRs, new pushes, and new mentions.