👷 Run checks on Woodpecker

[Vilos92]

Runs the JS and Rust CI checks on the greg-zone Woodpecker instance instead of GitHub Actions.

After one shared bun install (bun-git image), format, lint, comment-format, typecheck and the fallow audit fan out in parallel. rust-fmt and clippy run in a new local greg-zone/gdex-rust image (rust 1.95.0 with rustfmt, clippy and the Tauri Linux libraries) and start immediately, needing no bun install. Rust steps invoke cargo directly since the bun scripts are thin wrappers.

The desktop-macos Tauri .app bundle build stays in .github/workflows/builds.yaml on GitHub Actions — a Linux Docker backend cannot produce a macOS bundle. Both composite actions under .github/actions/ are kept for that workflow.

Rehearsed locally against a simulated merge of this branch into main: all JS checks green (fallow diffing HEAD^1), and both Rust checks green (clippy 0 warnings) in the new image.

🤖 Generated with Claude Code

[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: 26 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: af85ae51-ace9-4d83-b631-df401c71f5c1

📥 Commits

Reviewing files that changed from the base of the PR and between 6c1524d and 0956d9c.

📒 Files selected for processing (2)

• .github/workflows/continuous-integration.yaml
• .woodpecker.yml

---

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