Overview

We should add automated linting to our Continuous Integration (CI) pipeline to ensure consistent code style and catch potential errors early in the development process.

Current Situation

• Currently, there is no automated linting in our CI pipeline.
• Code style inconsistencies are being caught manually during code reviews.
• We have .eslintrc.json and .prettierrc.json files in our repository, but they are not enforced automatically.

Proposed Solution

Add a linting step to our GitHub Actions workflow that runs on every pull request and push to main branches.

Implementation Details

1. Create or update a GitHub Actions workflow file (e.g., .github/workflows/ci.yml).
2. Add a linting job that includes:
   • Setting up Node.js
   • Installing dependencies
   • Running ESLint
   • (Optional) Running Prettier