Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Improve CI Pipelines: Linting, Formatting, Pre-commits, and Testing

Open
#458 0 comments 0 reactions 1 assignee View on GitHub

@sahilds1 is already working on this.

Since Jul 8, 2026.

Assessment

This issue has not been assessed yet.

Description

Documentation

The current CI workflows in .github/workflows/frontend-ci.yml and .github/workflows/python-app.yml are missing several critical quality checks.

Proposed Improvements:
1. Frontend (frontend-ci.yml)
  • Strict Checks: Remove continue-on-error: true from Lint and Build steps so that PRs cannot be merged with failures.
  • Formatting: Add a step to verify formatting using Prettier (e.g., npx prettier --check .).
  • Testing: Add a step to run tests if any exist (e.g., npm test).
  • Dependency Cache: Ensure Node.js cache is working correctly (already present but should be verified).
2. Python Backend (python-app.yml)
  • Formatting: Add Ruff formatting check (ruff format --check).
  • Testing: Add a step to run Django tests (python manage.py test).
  • Branch Triggers: Update branch triggers to include develop or the main branch (currently points to listOfMed).
  • Linting: Improve Ruff linting configuration or ensure it's running with the desired rules.
3. General Enhancements
  • Pre-commit Hooks: Integrate pre-commit into CI to ensure all hooks pass before merging.
  • Consistency: Align branch triggers across all CI workflows.
Why is this needed?

To ensure code quality, consistency, and prevent regressions from being merged into the main branches.

Dominant language
TypeScript
Stars
21
Forks
19
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeForPhilly/balancer-main

All issues in CodeForPhilly/balancer-main

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.