Benny Joo
ab21c7f805
* 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>
950 B
950 B
title, impact, impactDescription, tags
| title | impact | impactDescription | tags |
|---|---|---|---|
| Code Review Focus | MEDIUM | Focused reviews are more useful than scattered feedback | code-review, workflow |
Code Review Focus
When Asked to Review a PR
Focus on providing a clear summary of what the PR is doing and its core functionality.
Avoid getting sidetracked by:
- CI failures
- Testing issues
- Technical implementation details (unless specifically requested)
Good Review Structure
- Summary: What does this PR do?
- Core changes: What are the main code changes?
- Impact: What parts of the system does this affect?
What to Look For
- Does the code do what it claims to do?
- Are there any obvious bugs or edge cases?
- Does it follow Cal.diy coding standards?
- Is the change appropriately scoped?
What to Skip (Unless Asked)
- Nitpicks about style (Biome handles this)
- Suggestions for refactoring unrelated code
- Deep dives into implementation details