Skip to content

ci: add landing-build job to verify agentwatch-landing app#618

Merged
sreerevanth merged 1 commit into
sreerevanth:mainfrom
pavsoss:issue-609-landing-ci
Jul 14, 2026
Merged

ci: add landing-build job to verify agentwatch-landing app#618
sreerevanth merged 1 commit into
sreerevanth:mainfrom
pavsoss:issue-609-landing-ci

Conversation

@pavsoss

@pavsoss pavsoss commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Closes #609

This PR addresses the missing CI coverage for the Next.js 16 landing page application.

  • Added landing-build job: Appended a new build job to .github/workflows/ci.yml that mirrors the frontend-build job, but runs against agentwatch-landing.
  • Validation: Ensures agentwatch-landing is properly checked out, dependencies are installed using npm ci, and the app builds successfully on every pull request, preventing unverified dependency or type errors from slipping into main.

@vercel

vercel Bot commented Jul 12, 2026

Copy link
Copy Markdown

@pavsoss is attempting to deploy a commit to the sreerevanth's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 30 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 30b718f1-bd28-46e0-91f0-67615b9ef623

📥 Commits

Reviewing files that changed from the base of the PR and between 9559520 and 2db507b.

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

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

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

@github-actions

Copy link
Copy Markdown
Contributor

🧪 PR Test Results

Check Result
Tests (pytest tests/) ✅ success
Lint (ruff check .) ❌ failure
Coverage (agentwatch) 74.70%

Python 3.12 · commit 2db507b

@vercel

vercel Bot commented Jul 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
agent-watch Ready Ready Preview, Comment Jul 14, 2026 6:03pm

@sreerevanth sreerevanth merged commit 3ddddba into sreerevanth:main Jul 14, 2026
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CI] agentwatch-landing is never built or type-checked in CI

2 participants