🔄 synced file(s) with dianlight/opencode-actions

[dianlight]

synced local file(s) with dianlight/opencode-actions.

Changed files

• synced local .github/workflows/opencode.yml with remote .github/workflows/opencode.yml
• synced local .github/workflows/opencode-review.yaml with remote .github/workflows/opencode-review.yaml
• synced local .github/workflows/opencode-triage.yaml with remote .github/workflows/opencode-triage.yaml

---

This PR was created automatically by the repo-file-sync-action workflow run #28621931504

[coderabbitai]

Warning

Review limit reached

@dianlight, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 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

Run ID: 6af8fcbd-5a06-44d7-8459-2d3b16fb941b

📥 Commits

Reviewing files that changed from the base of the PR and between bebb359 and 7ac6a04.

📒 Files selected for processing (3)

• .github/workflows/opencode-review.yaml
• .github/workflows/opencode-triage.yaml
• .github/workflows/opencode.yml

📝 Walkthrough

Walkthrough

This PR modifies two GitHub Actions workflows. The opencode-review workflow changes its trigger condition to check author_association (OWNER/MEMBER/COLLABORATOR) instead of excluding bot logins, and switches from explicit GITHUB_TOKEN/TOKEN env vars to use_github_token, with prompt formatting adjustments. The opencode-triage workflow renames a secret env key.

Changes

Opencode Workflow Updates

Layer / File(s)	Summary
Review trigger and token gating .github/workflows/opencode-review.yaml	Job condition now checks author_association (OWNER/MEMBER/COLLABORATOR) instead of excluding renovate/dependabot logins; GITHUB_TOKEN/TOKEN env vars commented out in favor of use_github_token: true; prompt block reformatted.
Triage secret key rename .github/workflows/opencode-triage.yaml	Env variable key changed from ANTHROPIC_API_KEY to OPENCODE_API_KEY, still sourced from secrets.OPENCODE_API_KEY.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description only notes the sync source and changed files; it omits most required template sections like type, testing, documentation, and issues.	Fill out the template sections for Description, Type of Change, Changes Made, Testing, Documentation, Breaking Changes, Related Issues, Screenshots/Examples, Checklist, and Reviewer Notes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title accurately reflects that workflow files were synced from dianlight/opencode-actions.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch repo-sync/opencode-actions/default

---

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

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/opencode-review.yaml:
- Around line 20-28: The opencode review step is enabled with use_github_token:
true but the GITHUB_TOKEN env var is commented out, so the action cannot
authenticate to post comments. In the workflow step using
anomalyco/opencode/github, restore env.GITHUB_TOKEN from secrets.GITHUB_TOKEN
while keeping use_github_token: true so the action can read the token it
expects.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4d434b6d-2cb8-4bd1-aef8-c78a3daee5d8

📥 Commits

Reviewing files that changed from the base of the PR and between a8f1200 and bebb359.

📒 Files selected for processing (2)

• .github/workflows/opencode-review.yaml
• .github/workflows/opencode-triage.yaml

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.27%. Comparing base (a8f1200) to head (7ac6a04).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #752      +/-   ##
==========================================
+ Coverage   43.24%   43.27%   +0.03%     
==========================================
  Files         297      297              
  Lines       29779    29779              
  Branches     1932     1932              
==========================================
+ Hits        12879    12888       +9     
+ Misses      14964    14952      -12     
- Partials     1936     1939       +3     

Flag	Coverage Δ
backend	39.20% <ø> (+0.03%)	⬆️
custom-component	43.27% <ø> (+0.03%)	⬆️
frontend	55.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

I've reviewed all three files. Here's my analysis:

---

🛠️ [QUALITY] Trailing whitespace added to blank prompt lines

In opencode-review.yaml, the blank lines within the prompt: block (lines 35, 37, 39, 41, 43) now contain trailing whitespace. While functionally identical in a YAML multi-line string, this is unnecessary noise that can cause diff churn and triggers linter warnings in most editors.

Suggest stripping trailing whitespace from blank lines within the prompt block

          prompt: |
            Act as an expert Senior Software Engineer and Code Reviewer. Review this pull request thoroughly based strictly on the provided diff and its immediate context.

            Follow these strict directives:

            1. **Targeted Comments & Suggestions:** Apply your feedback directly to the specific changed files and lines. When proposing a concrete code change, do not just leave a plain text comment; instead, open a formal change request using GitHub's suggestion blocks (```suggestion ... ```) to initiate a focused discussion that the author can easily review or commit.

            2. **Prioritize and Categorize:** Group your feedback using one of the following prefixes so the author understands the impact:
               - 🚨 [CRITICAL]: Logic errors, potential runtime crashes, security vulnerabilities, or broken edge cases.
               - ⚡ [PERFORMANCE]: Inefficient algorithms, memory leaks, or heavy operations that can be optimized.
               - 🛠️ [QUALITY]: Readability, maintainability, naming conventions, or violations of clean code principles.
               - 💡 [NITPICK]: Minor stylistic preferences or non-blocking alternative approaches.

            3. **Be Actionable:** Do not just point out a problem. Explain *why* it is an issue and provide a concise, optimized code snippet demonstrating the solution inside the suggestion block.

            4. **Tone and Noise Control:** Be direct, objective, and constructive. Avoid generic praise (e.g., "Good job here") or conversational fluff. If a file looks great, do not leave empty or redundant comments.

---

💡 [NITPICK] Commented-out TOKEN env var in opencode-review.yaml

Line 24 has #TOKEN: ${{ secrets.GITHUB_TOKEN }} — dead code documenting legacy behavior. Since use_github_token: true now uses GITHUB_TOKEN (set on line 23), the old TOKEN var is never read. Consider removing it to keep the workflow clean.

          OPENCODE_API_KEY: ${{ secrets.OPENCODE_API_KEY }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

---

Summary of what's good

Change	Verdict
opencode.yml permissions (read → write)	✅ Correct — required for the action to post comments/PRs
opencode-review.yaml trigger (login substring → author_association)	✅ Correct — more secure and explicit, avoids running on external PRs
use_github_token: true + GITHUB_TOKEN	✅ Correct — per opencode docs this is the valid combo
opencode-triage.yaml env rename (ANTHROPIC_API_KEY → OPENCODE_API_KEY)	✅ Correct — aligns env var name with the actual secret source

No critical or blocking issues. The trailing whitespace is the only actionable finding.

opencode session  |  github run