chore: update dependency config to monitor multiple locations

[shenxianpeng]

Address #302 (comment)

We can use directories to update github-actions files across multiple locations

But the only issue is that we can not test the action from docs/examples folder.

Summary by CodeRabbit

• Chores
  • Expanded dependency automation to cover additional areas of the project, ensuring broader and more timely updates across workflows and example assets.
  • Kept update cadence, grouping rules, and dependency types unchanged to avoid unexpected behavior.
  • Improves maintenance reliability and security of automated updates without affecting application features or user workflows.

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Updated .github/dependabot.yml to replace the single root directory: / for the github-actions updates with a directories: list containing / and docs/examples; all other dependabot settings remain unchanged.

Changes

Cohort / File(s)	Summary
Dependabot configuration .github/dependabot.yml	Replaced directory: / for github-actions with directories: ["/", "docs/examples"]; version, schedule, groups, and pip update block unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

📜 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 1858b23 and 1962b87.

📒 Files selected for processing (1)

• .github/dependabot.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/dependabot.yml

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch shenxianpeng-patch-1

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[Copilot]

Pull Request Overview

This PR updates the Dependabot configuration to monitor GitHub Actions files across multiple directories instead of just the root directory. The change enables automatic dependency updates for both the main workflows and example workflows.

• Changes Dependabot to use directories instead of directory to monitor multiple locations
• Adds monitoring for both .github/workflows and docs/examples directories

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0769e8f and 1858b23.

📒 Files selected for processing (1)

• .github/dependabot.yml (1 hunks)

🔇 Additional comments (1)

.github/dependabot.yml (1)

9-11: Ignore absolute-path suggestion for directories

Dependabot’s directories entries must be repo-relative (no leading slash). The existing paths

".github/workflows"
"docs/examples"

are correct and should not be changed to "/.github/workflows" or "/docs/examples".

Likely an incorrect or invalid review comment.

[shenxianpeng]

We may need to cut a new release to clear the backlog and maintain the release cadence once this PR is merged.

(I will manually trigger dependency to test this PR after merge)

[2bndy5]

If dependabot does not like this patch we can always revert it and move the example workflows from docs/examples to .github/workflows/examples

[shenxianpeng]

I expect another bump version PR to be created by this run https://github.com/cpp-linter/cpp-linter-action/actions/runs/16904279566/job/47890296111, but it did not happen.

updater | 2025/08/12 09:08:09 INFO <job_1073907439> Found no dependencies to update after filtering allowed updates in /
updater | 2025/08/12 09:08:09 INFO <job_1073907439> Found no dependencies to update after filtering allowed updates in /docs/examples

[2bndy5]

Its strange. Looking at those logs, I see a lot of garbage that is not useful to us as consumers. However, I did find the following logs:

2025/08/12 09:08:00 INFO <job_1073907439> Updating the /docs/examples directory.
...
updater | 2025/08/12 09:08:02 INFO <job_1073907439> Checking if actions/checkout 4 needs updating
updater | 2025/08/12 09:08:02 INFO <job_1073907439> Available release version/ref is 5
2025/08/12 09:08:02 INFO <job_1073907439> Latest version is 5
2025/08/12 09:08:02 INFO <job_1073907439> Adding dependencies as handled: (actions/checkout).
...
updater | 2025/08/12 09:08:04 INFO <job_1073907439> Creating dependency change for actions/checkout (5) in group actions
updater | 2025/08/12 09:08:04 INFO <job_1073907439> Updating actions/checkout from 4 to 5
updater | 2025/08/12 09:08:05 INFO <job_1073907439> Creating a pull request for 'actions'
...
updater | 2025/08/12 09:08:09 INFO <job_1073907439> Found no dependencies to update after filtering allowed updates in /
updater | 2025/08/12 09:08:09 INFO <job_1073907439> Found no dependencies to update after filtering allowed updates in /docs/examples
updater | 2025/08/12 09:08:09 INFO Results:
+--------------------------------------------+
| Changes to Dependabot Pull Requests |
+---------+----------------------------------+
| created | actions/checkout ( from 4 to 5 ) |
+---------+----------------------------------+

Not sure why we are not seeing this alleged PR. I'm also not sure what "filtering allowed updates" means.

Plan B

We could instead move the workflows from docs/examples to .github/workflows/examples. That should achieve what we wanted here. But the docs source needs to be updated for the changed paths. There might be a complication from mkdocs about using sources outside the docs/ folder...