Add GitHub Actions CI workflow: lint and build

[Lakshmipriya0812]

Fixes #2

CI Details

1. CI runs automatically on:

• Every push
• Every pull request

2. PRs will fail if linting or build fails
3. Uses dummy environment variables for Firebase and Resend (as agreed)

CD Notes

• Deployment is handled via Vercel’s native GitHub integration
• No deployment steps are added to GitHub Actions
• Production deployment access and configuration will be handled by maintainers

Notes

• ESLint currently reports warnings for unused imports (no errors)
• These warnings do not block CI and can be addressed incrementally

[Lakshmipriya0812]

@ghanshyam2005singh Hi, the CI workflow is set up and ready. Since this PR is from a fork, it requires maintainer approval to run. Could you please approve it so we can see the CI results?

[ghanshyam2005singh]

Done ✅
Update the node version and also link the issue this PR solves

[Lakshmipriya0812]

the README mentions Node.js 18.x as the required version, but next build fails with Node.js 18.20.8, stating Next.js requires Node.js >= 20.9.0. Could you please confirm which Node.js version we should use for CI and local development?

[ghanshyam2005singh]

README file and other file is just a basic setup, it has lots of issues. Use the node version >=20.9.0 or 22.x

[Lakshmipriya0812]

The CI workflow (lint + build) is now complete and running successfully.

[Lakshmipriya0812]

I just wanted to clarify that, as a contributor, I don’t have access to trigger production deployments on Vercel. I can definitely help with setting up CD workflow files, documentation, or configuration suggestions, but the actual deployment would need to be handled by someone with access.

[ghanshyam2005singh]

No issue, just update the PR description with issue number it fixes and CD workflow files and configuration, rest we will handle.