Skip to content

Feature: Set up CI Pipeline #97 - #100

Merged
Manastirski merged 22 commits into
mainfrom
feature/97-Set-up-CI-Pipeline
Jul 16, 2026
Merged

Feature: Set up CI Pipeline #97#100
Manastirski merged 22 commits into
mainfrom
feature/97-Set-up-CI-Pipeline

Conversation

@Manastirski

Copy link
Copy Markdown
Contributor

CI:

  • Add .github/workflows/ci.yml: lint (non-blocking), unit tests, build
  • Run on push (except main) and PRs targeting main
  • Add uniplanWeb/.nvmrc as single source of truth for Node version
  • Require build-and-test as a required PR status check (branch protection)

Lint:

  • Migrated constructor DI to inject() across all flagged components/services
  • Removed unused imports/params
  • Typed faculty-service.ts responses (void, per backend contract)
  • Left major-service.ts any types as warnings fix tracked in #Bug: resolve no-explicit-any warnings after facade migrations merge #99, blocked on in-progress backend facade migrations
  • Disabled prefer-on-push-component-change-detection for now, the application is not so big that eagerly detecting changes causes problems, for now.

…eads Node version from .nvmrc instead of hardcoding it, keeping local and CI environments in sync from one file.
- Add .github/workflows/ci.yml: lint (non-blocking), unit tests, build
- Run on push (except main) and PRs targeting main
- Add uniplanWeb/.nvmrc as single source of truth for Node version
- Require build-and-test as a required PR status check (branch protection)

Lint:
- Migrated constructor DI to inject() across all flagged components/services
- Removed unused imports/params
- Typed faculty-service.ts responses (void, per backend contract)
- Left major-service.ts `any` types as warnings — fix tracked in ##99, blocked on in-progress backend facade migrations
- Disabled prefer-on-push-component-change-detection for now (perf refactor, out of scope)
@Manastirski
Manastirski requested a review from a team as a code owner July 2, 2026 13:04
- Trigger only on pull_request (opened/synchronize/reopened) instead of
  push+pull_request, so pushing to a PR branch no longer runs the
  pipeline twice; covers forks too
- Add concurrency group to cancel superseded runs on the same PR/branch
- Bump actions/checkout and actions/setup-node to v5 (Node 20 runtime
  deprecation warning)
- Add timeout-minutes: 10 to stop a hung job from running indefinitely
- Write coverage % and initial bundle size to the job summary
- Skip the pipeline on docs-only PRs (**.md, .claude/**)
- Drop initial bundle size section
- Add full lint output (per-file rule violations + problem count) to
  the job summary so warnings/errors are visible without opening logs
DjesikaV
DjesikaV previously approved these changes Jul 6, 2026

@DjesikaV DjesikaV left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I verified the CI commands locally

PIPetkova19
PIPetkova19 previously approved these changes Jul 7, 2026
Comment thread uniplanWeb/eslint.config.js
…d it, fixed all the methods with no return type so eslint runs with 0 errors.
@Manastirski
Manastirski dismissed stale reviews from PIPetkova19 and DjesikaV via aa1b9b1 July 14, 2026 10:50
@Manastirski
Manastirski merged commit 3eb15ec into main Jul 16, 2026
1 check passed
@Manastirski
Manastirski deleted the feature/97-Set-up-CI-Pipeline branch July 16, 2026 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants