feat: add Dependabot for GitHub Actions (#15)

[rmems]

Closes #15

Adds Dependabot config for GitHub Actions. Cargo deps will be added when needed.

---

Greptile Summary

This PR adds Dependabot configuration for GitHub Actions updates. The main changes are:

• Weekly updates for the github-actions ecosystem.
• Repository-root workflow scanning with directory: "/".
• A dependencies label for Dependabot PRs.
• A commented placeholder for future Cargo updates.

Confidence Score: 5/5

This looks safe to merge.

• The Dependabot schema and GitHub Actions directory setting look correct.
• The only follow-up is making sure the configured label exists if label-based automation depends on it.

Important Files Changed

Filename	Overview
.github/dependabot.yml	Adds weekly Dependabot updates for GitHub Actions with a custom PR label.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
.github/dependabot.yml:11-12
**Missing Label Drops Triage**

Dependabot only applies custom labels that already exist in the repository. If `dependencies` has not been created yet, these update PRs are still opened but arrive unlabeled, so any triage, auto-merge, or notification rule keyed on that label will not run.

_{Reviews (1): Last reviewed commit: "feat: add Dependabot for GitHub Actions ..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 21 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 46afd090-c558-4eac-9360-2efc6ffaf9f6

📥 Commits

Reviewing files that changed from the base of the PR and between 2e16e45 and 562d1ae.

📒 Files selected for processing (1)

• .github/dependabot.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/dependabot

---

_{Comment @coderabbitai help to get the list of available commands.}

[amazon-q-developer]

The Dependabot configuration is properly structured and follows GitHub's recommended practices. The configuration correctly sets up automated updates for GitHub Actions with appropriate scheduling and labeling. No blocking issues identified.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[gemini-code-assist]

Code Review

This pull request introduces a Dependabot configuration file (.github/dependabot.yml) to enable weekly automated dependency updates for GitHub Actions. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[greptile-apps]

Missing Label Drops Triage

Dependabot only applies custom labels that already exist in the repository. If dependencies has not been created yet, these update PRs are still opened but arrive unlabeled, so any triage, auto-merge, or notification rule keyed on that label will not run.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/dependabot.yml
Line: 11-12

Comment:
**Missing Label Drops Triage**

Dependabot only applies custom labels that already exist in the repository. If `dependencies` has not been created yet, these update PRs are still opened but arrive unlabeled, so any triage, auto-merge, or notification rule keyed on that label will not run.

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[kilo-code-bot]

Code Review Summary

Status: No New Issues Found | Recommendation: Already merged — no new findings

Files Reviewed (1 file)

• .github/dependabot.yml

Notes

• The labels: ["dependencies"] entry relies on a dependencies label existing in the repository; Dependabot still opens PRs but leaves them unlabeled when the label is missing, which can break label-based triage/auto-merge/notification rules. This concern is already tracked by an existing active inline comment on .github/dependabot.yml:12, so Kilo did not post a duplicate. (Kilo could not query the repo's label list in this environment to confirm whether the label exists — assumption noted.)
• No other new issues found in the changed code. version: 2, directory: "/", and interval: "weekly" are valid Dependabot v2 syntax; the commented-out cargo block is an intentional placeholder.

---

_{Reviewed by GLM-5.2 · Input: 23.3K · Output: 5.7K · Cached: 184K}