feat/workflow : added ci pipeline

[mizurex]

added ci workflow for lint and build
you can add more steps later if needed

i have only covered the usual paths that get prs (web, docs, packages).

• Tested this workflow

@apsinghdev @ajeetunc if this looks fine you can set up the maintainer approve workflow, otherwise feel free to close it. thanks :)

Summary by CodeRabbit

• Chores
  • Added an automated CI pipeline that runs on pull requests to validate changes. It performs dependency install, linting, and a build to provide faster feedback and ensure code quality before merging. Concurrency control added to avoid overlapping runs for the same PR.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

@mizurex is attempting to deploy a commit to the AJEET PRATAP SINGH's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

Adds a new GitHub Actions workflow at .github/workflows/ci.yaml that runs on pull requests to main for specified paths, sets read-only contents permission and concurrency, and executes checkout, pnpm v10.11.0 and Node.js v22 setup, install (frozen lockfile), lint, and build steps.

Changes

Cohort / File(s)	Summary
CI Workflow Configuration ​.github/workflows/ci.yaml	New GitHub Actions workflow named ci triggered on pull requests to main for apps/web/**, apps/docs/**, packages/**, and .github/workflows/**; sets contents: read, concurrency group pr-ci-${{ github.ref }} with cancel-in-progress; job runs on ubuntu-latest and performs checkout, pnpm v10.11.0 setup, Node.js v22 setup (cache: pnpm), pnpm install --frozen-lockfile, lint, and build steps.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify branch and path filter patterns are intentional and complete.
• Confirm Node.js v22 and pnpm v10.11.0 compatibility with project.
• Check use of contents: read permission and whether additional permissions are required.
• Ensure concurrency group naming and cancel-in-progress behavior align with CI expectations.
• Confirm referenced action versions (checkout@v4, setup-node@v4) are acceptable.

Poem

🐰 A tiny workflow hops in stride,
On each PR it checks and tries,
It installs, lints, and builds with glee,
Cancelling echoes that disagree,
A rabbit's cheer for CI skies 🎉

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and clearly describes the main change: adding a CI pipeline workflow to the GitHub Actions configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bcb9e2c and 1dfa3a9.

📒 Files selected for processing (1)

• .github/workflows/ci.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/ci.yaml

---

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 and usage tips.}