Skip to content

Modify update triggers in bulldozer.yml - #7

Merged
phuongfi91 merged 1 commit into
mainfrom
feat/phuongfi91/bulldozer-config
Aug 28, 2026
Merged

phuongfi91 merged 1 commit into
mainfrom
feat/phuongfi91/bulldozer-config

Conversation

@phuongfi91

Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: Phuong Nguyen <7949163+phuongfi91@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings August 28, 2026 12:12
@phuongfi91
phuongfi91 merged commit db69c39 into main Aug 28, 2026
@phuongfi91
phuongfi91 deleted the feat/phuongfi91/bulldozer-config branch August 28, 2026 12:12
@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can reply 'qodo' on any finding to push back, ask questions, or dig deeper

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Make Bulldozer updates label-driven across branches

⚙️ Configuration changes 🕐 Less than 5 minutes

Grey Divider

AI Description

• Adds dependencies as a Bulldozer update-trigger label.
• Stops target branches from automatically triggering pull request updates.
• Applies update eligibility consistently regardless of the target branch.
Diagram

graph TD
  A["Pull request"] --> B{"Trigger label?"} -->|Yes| C{"Ignored label?"} -->|No| D["Update branch"]
  B -->|No| E["No update"]
  C -->|Yes| E
Loading
High-Level Assessment

The label-driven approach is appropriate because it removes broad branch-based updates while explicitly opting dependency pull requests into updates. Retaining branch triggers would undermine that control, and adding branch-specific exclusions would be more complex without providing a clear benefit.

Files changed (1) +1 / -4

Other (1) +1 / -4
bulldozer.ymlMake update triggers label-based across all branches +1/-4

Make update triggers label-based across all branches

• Adds the 'dependencies' label to Bulldozer's update triggers. Removes target-branch triggers so pull requests are updated through explicit labels rather than merely targeting dev, main, develop, or master.

bulldozer.yml

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Bulldozer configuration to adjust which pull requests are eligible for automated branch updates.

Changes:

  • Expanded the update.trigger.labels list to include the dependencies label.
  • Removed the (previously present) branch-targeting trigger lines from the update section.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants