Skip to content

ci: Optimize CI pipeline by parallelizing workflow jobs#160

Open
Emrys02 wants to merge 2 commits into
BuidlZone-Labs:mainfrom
Emrys02:main
Open

ci: Optimize CI pipeline by parallelizing workflow jobs#160
Emrys02 wants to merge 2 commits into
BuidlZone-Labs:mainfrom
Emrys02:main

Conversation

@Emrys02

@Emrys02 Emrys02 commented Jul 12, 2026

Copy link
Copy Markdown
  • Workflow no longer trigger on commit to the main branch
  • Build, Test and Lint Check has been split into separate concurrent jobs
  • Workflow now prevents multiple instances from spawning
  • Result job has been introduced which passes or fails the workflow based on the result of the prior job with Build and Test taking precedence over Lint Check

Closes #130

Summary by CodeRabbit

  • Tests

    • Added a dedicated automated test job to validate changes.
  • Chores

    • Updated continuous integration to run for pull requests.
    • Added consolidated status reporting for build, lint, and test results.
    • Prevented outdated workflow runs from continuing when newer changes are submitted.

@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

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

Next review available in: 55 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: 30bc89b5-37e5-4b67-aea8-4bf7edd7e8cc

📥 Commits

Reviewing files that changed from the base of the PR and between 45696e2 and 19ad35b.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml
📝 Walkthrough

Walkthrough

The CI workflow now runs only for pull requests, cancels superseded runs, separates tests from build and lint jobs, and adds an always-running result job that reports outcomes and enforces build and test success.

Changes

CI validation workflow

Layer / File(s) Summary
Workflow triggers and validation jobs
.github/workflows/ci.yml
The workflow uses pull request triggers and concurrency cancellation, with updated build and lint job definitions.
Test and aggregate result jobs
.github/workflows/ci.yml
Tests run in a dedicated job, and an always-running result job reports build, lint, and test outcomes while failing when build or tests fail.

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

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: the CI workflow was reworked to run jobs in parallel.
✨ 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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
.github/workflows/ci.yml (1)

11-65: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚖️ Poor tradeoff

Consider extracting shared setup steps into a composite action.

The checkout, Node setup, and npm ci steps are duplicated across build, lint, and tests. Extracting these into a reusable composite action would reduce duplication and simplify future updates (e.g., changing Node version or cache config in one place).

🤖 Prompt for 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.

In @.github/workflows/ci.yml around lines 11 - 65, Extract the duplicated
checkout, Node.js setup, and npm ci steps from the build, lint, and tests jobs
into a reusable composite action. Update each job to invoke that action while
preserving the existing Node version, npm cache configuration, and dependency
installation behavior.
🤖 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/ci.yml:
- Around line 16-17: Fix the checkout step indentation in the workflow so the
uses entry is nested under the same list item as name: Checkout. Update the
checkout step structure without changing the action reference, ensuring it forms
one valid step with both name and uses.

---

Nitpick comments:
In @.github/workflows/ci.yml:
- Around line 11-65: Extract the duplicated checkout, Node.js setup, and npm ci
steps from the build, lint, and tests jobs into a reusable composite action.
Update each job to invoke that action while preserving the existing Node
version, npm cache configuration, and dependency installation behavior.
🪄 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 Plus

Run ID: cbe4c099-b806-4a19-9664-062495863e83

📥 Commits

Reviewing files that changed from the base of the PR and between 95b975e and 45696e2.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml

Comment thread .github/workflows/ci.yml Outdated
@drips-wave

drips-wave Bot commented Jul 12, 2026

Copy link
Copy Markdown

@Emrys02 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

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.

Optimize CI pipeline by parallelizing workflow jobs

1 participant