Skip to content

ci: build + test on pull requests to main - #2

Merged
cristim merged 1 commit into
mainfrom
ci/github-actions
Oct 4, 2026
Merged

cristim merged 1 commit into
mainfrom
ci/github-actions

Conversation

@cristim

@cristim cristim commented Jul 17, 2026

Copy link
Copy Markdown
Member

What

Adds a CI workflow that runs on every pull request and push to main:

  • installs root dependencies (npm ci)
  • builds the CLI (npm run build)
  • runs the backend test suite (npm test)
  • installs GUI dependencies and runs the GUI test suite

Why

We're moving to a PR-based workflow. This gives every PR an automated
build + test gate before merge.

Notes

  • Runs on ubuntu-latest. The LibreOffice/PDF tests already tolerate
    LibreOffice being absent, so they stay green on the runner.
  • The GUI build (tsc && vite build) is intentionally not run yet: tsc
    currently errors on a pre-existing baseUrl deprecation. CI runs the GUI
    tests (vitest) instead. Fixing the GUI tsconfig can be a follow-up.
  • Once this merges, I'll enable branch protection on main requiring this
    check to pass.

Add a CI workflow that installs deps, builds the CLI, and runs the backend
and GUI test suites on every pull request and push to main, so PRs are
validated before merge.
@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown

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: 43 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: 0c09b291-a62f-45db-b1e6-cd76b8226d96

📥 Commits

Reviewing files that changed from the base of the PR and between 4305c3b and effc5a3.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/github-actions

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

@cristim
cristim merged commit 4e62ed0 into main Oct 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant