Skip to content

CI Pipeline: Automated checks for PRs #84

Closed

Description

@Ayush8923

Is your feature request related to a problem?
Currently, there is no automated CI process to validate code quality or ensure successful project builds on each PR or push. This can result in lint errors or build failures being overlooked until later stages.

Describe the solution you'd like
Set up a CI pipeline (e.g., GitHub Actions) to automatically run the following checks on every pull request and push:

  • Run lint check:

    npm run lint  
    
  • Run build check:

    npm run build  
    

Expected Outcome

  • CI runs automatically on each PR
  • PRs fail if lint or build fails
  • Improved code reliability and stability
Original issue

Describe the current behavior
Currently, there is no automated CI process to validate code quality or ensure the project builds successfully on each PR or push. This can lead to issues such as lint errors or build failures going unnoticed until later stages.

Describe the enhancement you’d like
Set up a CI pipeline (e.g., GitHub Actions) to automatically run the following checks on every pull request and push:

  • Run lint check:
npm run lint
  • Run build check:
npm run build

Expected Outcome

  • CI runs automatically on each PR
  • PRs fail if lint or build fails
  • Improved code reliability and stability

Activity

  1. changed the title [-]CI Setup: Add Lint and Build Checks for Frontend[/-] [+]CI Pipeline: Automated checks for PRs[/+] on Mar 23, 2026
  2. moved this to To Do in Kaapi-devon Mar 23, 2026
  3. Ayush8923 commented on Mar 23, 2026

    @Ayush8923
    CollaboratorAuthor

    Additionally, we can also add a pre-commit hook for linting. This will help catch issues like unused variables or imports before the code is committed, ensuring better code and preventing such issues from reaching the repository.

  4. self-assigned this
    on Mar 23, 2026
  5. moved this from To Do to In Progress in Kaapi-devon Mar 23, 2026
  6. moved this from In Progress to In Review in Kaapi-devon Mar 24, 2026
  7. Ayush8923 commented on Mar 24, 2026

    @Ayush8923
    CollaboratorAuthor

    This has been completed. Closing this issue.
    PR reference: #85

  8. moved this from In Review to Closed in Kaapi-devon Mar 24, 2026
  9. closed this as completedby moving to Closed in Kaapi-devon Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

  • Status
    Closed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions