Files
cal-diy-oidc/agents/rules/ci-type-check-first.md
Benny Joo ab21c7f805 refactor: Cal.diy (#28903)
* feat: Cal.diy — community-driven MIT-licensed fork of Cal.com

This squashed commit contains all Cal.diy changes applied on top of calcom/cal.com main:

- Rebrand Cal.com to Cal.diy across the entire codebase
- Remove Enterprise Edition (EE) features, license checks, and AGPL restrictions
- Switch license from AGPL-3.0 to MIT
- Remove docs/ directory (migrated to Nextra at cal.diy)
- Remove dead code: org tests, EE tips, platform nav, premium username, SAML/SSO, etc.
- Clean up .env.example for self-hosted Cal.diy
- Update Docker image references to calcom/cal.diy
- Update README, CONTRIBUTING.md, and issue templates for Cal.diy community fork
- Add PR welcome bot for Cal.diy contributors
- Fix API v2 breaking changes oasdiff ignore entries
- Replace Blacksmith CI runners with default GitHub Actions

3893 files changed, 20789 insertions(+), 411020 deletions(-)

Co-Authored-By: benny@cal.com <sldisek783@gmail.com>

* refactor: remove org-specific /organizations/:orgId endpoints from API v2 atoms controllers (#1701)

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

* fix: revert Cal.diy Inc to Cal.com, Inc. in license files, copyright notices, and package metadata (#1702)

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

* rip out org related comments in api v2

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-04-15 09:52:36 -03:00

1.2 KiB

title, impact, impactDescription, tags
title impact impactDescription tags
Type Check Before Tests HIGH Type errors are often the root cause of test failures ci, typescript, type-check, workflow

Type Check Before Tests

Priority Order

When working on the Cal.diy repository, prioritize fixing type issues before addressing failing tests.

  1. Run yarn type-check:ci --force first
  2. Fix all TypeScript errors
  3. Then run tests with TZ=UTC yarn test

Why Type Check First

Type errors are often the root cause of test failures. Fixing types first:

  • Eliminates cascading failures
  • Ensures code compiles correctly
  • Catches issues that tests might miss

Comparing Branches

Compare type check results between the main branch and your feature branch to confirm whether you've introduced new type errors:

# On your branch
yarn type-check:ci --force 2>&1 | tee /tmp/feature-types.log

# On main
git checkout main
yarn type-check:ci --force 2>&1 | tee /tmp/main-types.log

# Compare
diff /tmp/main-types.log /tmp/feature-types.log

Missing Enum Errors

If you encounter errors related to missing enum values (like CreationSource.WEBAPP), running yarn prisma generate will typically resolve these issues by regenerating the TypeScript types from the schema.