[Feature] Setup Basic GitHub Actions CI Workflow for Pull Request Validation

[kunalverma2512]

Description

Currently, the repository does not have an automated workflow to validate Pull Requests before merging. As a result, broken builds, linting issues, or unstable changes may accidentally get merged into the main branch.

To improve repository stability and contribution workflow, we need to set up a basic GitHub Actions Continuous Integration (CI) workflow.

The initial CI setup should remain lightweight and beginner-friendly while still providing basic automated validation for Pull Requests.

The workflow should automatically:

• Install project dependencies
• Build the project
• Run basic lint checks

This will help contributors identify issues early while keeping the contribution process simple and accessible.

---

Requirements

Create the following workflow file:

.github/workflows/ci.yml

GitHub Actions CI Workflow Setup

Configure a GitHub Actions workflow that runs on Pull Requests targeting the main branch.

• Example structure:

  name: CI
  
  on:
    pull_request:
      branches:
        - main
  
  jobs:
    build:
      runs-on: ubuntu-latest
  
      steps:
        - uses: actions/checkout@v4
  
        - uses: actions/setup-node@v4
          with:
            node-version: 20
  
        - run: npm install
        - run: npm run build
        - run: npm run lint

• The workflow should:

  • Automatically run on Pull Request updates.
  • Validate that the project builds successfully.
  • Run basic lint checks to catch common issues.

Expected Outcome

After implementation:

• Pull Requests should automatically trigger basic validation checks.
• Broken builds should become easier to detect before merge.
• Contributors should receive immediate feedback for common issues.
• Repository stability and development workflow should improve.

Additional Notes

• This issue focuses only on setting up a basic CI workflow for initial Pull Request validation.
• Advanced validations such as automated testing, coverage enforcement, deployment checks, or strict quality gates can be introduced separately in future improvements.

[Harkiratcodess]

hi @kunalverma2512 can you assign this issue to me under GSSoC 2026