fix(gh-workflow): Include task files as dependencies in build_wheels workflow to trigger runs on changes.

[LinZhihao-723]

Description

Before this PR, task files are not included in the build wheel workflow. This causes a problem that the workflow (in particular, the linting workflow) is not triggered when the task files are changed.
This PR fixes the problem by properly including task files as dependencies in the build_wheels workflow.

Validation performed

• Ensure ci(clang-tidy): Enable clang-tidy for all C++ source files by automatically resolving paths under source directories (fixes #96). #124 will run build_wheels workflow as expected.

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow to trigger builds when specific configuration files are modified
  • Expanded workflow monitoring to include additional task and lint configuration files

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow file build_wheels.yml by expanding the trigger paths for pull requests and push events. Two new paths, lint-tasks.yml and Taskfile.yml, have been added to the workflow's trigger configuration. This change ensures that modifications to these specific files will now automatically initiate the build workflow, providing broader coverage for detecting and responding to changes in key project configuration files.

Changes

File	Change Summary
.github/workflows/build_wheels.yml	Added lint-tasks.yml and Taskfile.yml to workflow trigger paths

Possibly related PRs

• refactor: Update cmake file to fix the latest linting workflow failures. #123: Addresses failures in the linting workflow, complementing the expanded workflow trigger configuration

Suggested reviewers

• haiqi96

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 docstrings to generate docstrings for this PR. (Beta)
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/build_wheels.yml (1)

23-23: LGTM! Consider documenting the task files' purpose.

The mirrored configuration for push events is correct. Consider adding a comment in the workflow file to document why these task files are essential dependencies.

Add a comment above the paths section:

  pull_request:
+   # Paths that trigger the workflow:
+   # - Task files: Configuration for linting and development tasks
    paths:

Also applies to: 28-28

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4c963b8 and 4dacbd2.

📒 Files selected for processing (1)

• .github/workflows/build_wheels.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: linters

🔇 Additional comments (1)

.github/workflows/build_wheels.yml (1)

10-10: LGTM! Verify the task files exist in the repository.

The addition of task files to the trigger paths is correct and properly formatted.

Let's verify these files exist in the repository:

Also applies to: 15-15

✅ Verification successful

Task files exist and are correctly referenced

The workflow changes correctly reference both lint-tasks.yml and Taskfile.yml, which exist at the repository root.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the task files exist in the repository
# Expected: Both files should exist at the repository root

fd -t f -e yml '^(lint-tasks|Taskfile)\.yml$'

Length of output: 75