fix: github ci triggers

[biswapanda]

Overview:

1. examples have moved from examples/* to components/backend/*

closes: DYN-756

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• Chores
  • Updated CI workflow to monitor backend component directories instead of example directories for triggering specific jobs.

[coderabbitai]

Walkthrough

The update modifies the path filters in the .github/workflows/trigger_ci.yml GitHub Actions workflow. It removes example and Dockerfile paths from the vllm and sglang filters, replacing them with corresponding backend component directories. No other logic or workflow structure was changed.

Changes

File(s)	Change Summary
.github/workflows/trigger_ci.yml	Updated path filters for vllm and sglang to monitor backend component directories instead of example and Dockerfile paths.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub
    participant CI Workflow

    Developer->>GitHub: Push/PR with changes
    GitHub->>CI Workflow: Evaluate path filters
    alt Changes in components/backends/vllm/**
        CI Workflow->>CI Workflow: Trigger vllm jobs
    else Changes in components/backends/sglang/**
        CI Workflow->>CI Workflow: Trigger sglang jobs
    else Changes in other paths
        CI Workflow->>CI Workflow: No action for vllm/sglang
    end

Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• ci: Update trtllm gitlab triggers for new components directory and test script #1992: Updates CI workflow triggers to reflect backend component relocation, similar to this PR's path filter changes.
• refactor: Move TRTLLM example to the component/backends #1976: Reorganizes project structure by moving code from example directories to backend component directories, related to the path updates in this PR.
• ci: Add RUN_SGLANG to CI variables #1928: Modifies the same workflow file, refining which directories trigger CI jobs for vllm and sglang.

Poem

A hop to the backend, a skip from examples,
The CI now listens where real code rambles.
No Dockerfile here, no old paths to scan,
Just backend components—that’s now the plan!
With filters refined, our workflow’s in line,
The rabbit approves—review time is fine! 🐇✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eebc741 and 07edb30.

📒 Files selected for processing (1)

• .github/workflows/trigger_ci.yml (2 hunks)

🔇 Additional comments (2)

.github/workflows/trigger_ci.yml (2)

66-67: CI trigger path is correct for sglang backend

The workflow entry uses 'components/backends/sglang/**', which matches the actual directory components/backends/sglang. No updates are required.

Likely an incorrect or invalid review comment.

---

52-53: No update needed: ‘components/backends/vllm’ trigger path is correct

The repository layout under components uses the plural “backends” (as confirmed by the directory tree), so the existing filter

- 'components/backends/vllm/**'

will match and trigger CI as intended. No changes are required; please ignore the earlier suggestion.

Likely an incorrect or invalid review comment.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.