Files

T

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.3 KiB

Raw Permalink Blame History

title, impact, impactDescription, tags

title	impact	impactDescription	tags
CI Check Failure Handling	HIGH	Misinterpreting CI failures wastes debugging time	ci, debugging, workflow

CI Check Failure Handling

What to Focus On

When reviewing CI check failures in Cal.diy:

E2E tests can be flaky and may fail intermittently
Focus only on CI failures that are directly related to your code changes
Infrastructure-related failures (like dependency installation issues) can be disregarded if all code-specific checks pass

Known CI Issues to Ignore

These errors are related to SAML database misconfiguration on CI and should be ignored:

"password authentication failed for user postgres"
"Invalid URL"

E2E Tests Skipping

E2E tests skipping is expected behavior:

When E2E tests are skipped, it's because the ready-for-e2e label has not been added to the PR
The "required" check intentionally fails when E2E tests are skipped to prevent merging without E2E
Do not try to fix anything related to skipped E2E tests - this is completely expected and normal

Before Blaming CI

Always run type checks locally using yarn type-check:ci --force before concluding that CI failures are unrelated to your changes. Even if errors appear in files you haven't directly modified, your changes might still be causing type issues through dependencies or type inference.

1.3 KiB Raw Permalink Blame History