Modify trigger labels for auto-merge in bulldozer.yml

[phuongfi91]

No description provided.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[Copilot]

🟡 Changes recommended

The updated trigger criteria likely broadens auto-merge eligibility beyond the PR’s stated intent by removing branch scoping and making common labels sufficient to trigger merges.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates the repository’s Bulldozer auto-merge configuration to change which pull requests are eligible to be merged automatically.

Changes:

• Expanded merge.trigger.labels to include dependencies and trunk in addition to merge when ready.
• Commented out merge.trigger.branches, removing the explicit base-branch filter for triggering merges.

File summaries

File	Description
bulldozer.yml	Adjusts Bulldozer merge trigger criteria (labels and branch scoping).

Review details

Suppressed comments (1)

bulldozer.yml:28

• Commenting out merge.trigger.branches removes the target-branch guardrail for merges and makes the trigger apply to any base branch as long as another trigger matches. The PR title suggests only label behavior should change; if this wasn't intentional, restore the branch list (and extend it explicitly if you need additional branches).

    # Pull requests targeting any of these branches are added to the trigger.
    # branches: ["dev", "main", "develop", "master"]

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.