fix(lint): Correct glob pattern to recursively match all files.

[sitaowang1998]

Description

This pr fixes the bug that cpp-format-check and cpp-format-fix tasks are not re-executed on source file change.

The current sources for cpp-format-check uses dir/** to match for all files recursively under dir. However, in go-zglob, used by go-task, this glob only matches all first level entries under dir, while dir/**/* matches entries of all levels under dir.

This pr changes the glob matching so that all source files are included as sources of the tasks.

Checklist

• The PR satisfies the contribution guidelines.
• This is a breaking change and that has been indicated in the PR title, OR this isn't a
  breaking change.
• Necessary docs have been updated, OR no docs need to be updated.

Validation performed

• cpp-format-check and cpp-format-fix are re-executed on source file change.

Summary by CodeRabbit

• Chores
  • Enhanced file scanning within nested directories for automated quality checks, ensuring more comprehensive coverage without impacting user functionality.

[coderabbitai]

Walkthrough

This pull request modifies the file path patterns in the cpp-format-check task within the lint-tasks.yaml file. The original single-asterisk patterns have been updated to use a double asterisk followed by a trailing slash (/**/*), which allows recursive matching of files within subdirectories. The changes strictly adjust the linting configuration without altering the task’s dependencies or the declarations of exported or public entities.

Changes

File(s)	Change Summary
lint-tasks.yaml	Updated file path patterns for the cpp-format-check task from ** to /**/* for directories (G_EXAMPLES_DIR, G_SRC_SPIDER_DIR, and G_TEST_DIR), enabling recursive file matching.

Possibly related PRs

• chore: Add Taskfile tasks to lint C++ files. #9: Involved similar modifications to the cpp-format-check task configuration by adjusting file path patterns, directly relating to this update.

Suggested reviewers

• davidlion

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between db8332e and 67e441a.

📒 Files selected for processing (1)

• lint-tasks.yaml (1 hunks)

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

• GitHub Check: non-storage-unit-tests (ubuntu-24.04)
• GitHub Check: non-storage-unit-tests (ubuntu-22.04)
• GitHub Check: lint

🔇 Additional comments (1)

lint-tasks.yaml (1)

53-55: Update recursive glob patterns to include all subdirectories.

The change from using a single asterisk pattern to /**/* now properly captures files that are nested in any level within the target directories. This adjustment directly addresses the bug where changes in deeper directory levels were previously ignored in the cpp-format-check and cpp-format-fix tasks, aligning perfectly with the PR objectives.

---

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.
  • 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.