fix(ci): restrict merge pipeline to default/protected branches

[Teebor-Choka]

Summary

• Add branches filter to the merge workflow pull_request trigger to prevent it from running on PR-to-PR merges
• The workflow was triggering on all closed+merged PRs, including merges into non-default branches, wasting CI resources

[coderabbitai]

Warning

Rate limit exceeded

@Teebor-Choka has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 58 minutes and 41 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 58 minutes and 41 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: aff32592-1e4a-43d8-a0cf-4c3155de21a7

📥 Commits

Reviewing files that changed from the base of the PR and between d54abee and c79ed69.

📒 Files selected for processing (1)

• .github/workflows/merge.yaml

📝 Walkthrough

Walkthrough

A GitHub Actions workflow trigger filter has been added to the merge workflow. The pull_request event trigger for closed events is now restricted to pull requests targeting the main branch via a new branches: [main] configuration.

Changes

Cohort / File(s)	Summary
Workflow Trigger Configuration .github/workflows/merge.yaml	Added branches: [main] filter to pull_request event trigger to restrict closed event handling to the main branch only.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a branch filter to restrict the merge CI pipeline to run only on the default/protected branches.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kauki/fix/ci/merge-branch-filter

---

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 and usage tips.}

[Copilot]

Pull request overview

Restricts the “Merge” GitHub Actions workflow so it only triggers for PRs closed against the main branch, reducing CI usage for non-default-branch merges.

Changes:

• Added a pull_request.branches: [main] filter to the merge workflow trigger.
• Keeps existing job-level merged == true gating, but reduces unnecessary workflow triggers on non-main base branches.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The PR description says a base.ref check was added to all job conditions, but this change only adds an on.pull_request.branches: [main] filter; the job if: clauses are unchanged. Either update the description to match the implementation, or add github.event.pull_request.base.ref checks to the jobs (e.g., comparing against github.event.repository.default_branch if the intent is truly “default branch”).

[Copilot]

Hard-coding main here means the workflow will stop running if the repository’s default branch is renamed, and it doesn’t match the title’s “default/protected branches” wording. If you need this to follow the repo default branch, consider moving the branch restriction into job-level if: using github.event.repository.default_branch (or explicitly list all allowed base branches here if that’s the intent).