fix: add all blocking labels and manual dispatch to auto-queue

[omer-vishlitzky]

Summary

• Add missing blocking labels: do-not-merge/work-in-progress, do-not-merge/invalid-owners-file (both event-driven and scheduled jobs)
• Add workflow_dispatch trigger for manual re-queue runs (Actions > auto-queue > Run workflow)
• Supersedes fix: auto-queue re-enables auto-merge on ejected PRs #276

Blocking labels (full list)

Label	Effect
do-not-merge/hold	Disable auto-merge
do-not-merge/work-in-progress	Disable auto-merge
do-not-merge/invalid-owners-file	Disable auto-merge
needs-rebase	Disable auto-merge

Test plan

• PR with do-not-merge/work-in-progress label does not get auto-merge enabled
• Manual dispatch via Actions UI triggers requeue scan
• Scheduled run picks up ejected PRs

🤖 Generated with Claude Code

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: omer-vishlitzky

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [omer-vishlitzky]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Warning

Review limit reached

@omer-vishlitzky, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 1077abc7-12aa-45e4-92b6-a1c3772bb338

📥 Commits

Reviewing files that changed from the base of the PR and between 1ec4f25 and 1e28f82.

📒 Files selected for processing (1)

• .github/workflows/auto-queue.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[fullsend-ai-review]

🤖 Review · ⚠️ Cancelled · Started 11:27 PM UTC · Ended 11:30 PM UTC

Commit: 7fe717c · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 11:31 PM UTC · Completed 11:45 PM UTC

Commit: 1e28f82 · View workflow run →

[fullsend-ai-review]

Review skipped — this PR is already merged.

The /fs-review command only reviews open pull requests.

_{Posted by fullsend post-review check}