LogoLogo
CtrlK
  • πŸ‘‹Cal.com Handbook
  • The Company
    • ❓What is Cal.com?
    • πŸ“ˆMission, Vision and Values
    • πŸ…°οΈGlossary
    • πŸ“ˆOrganization Chart
  • HR & Careers
    • πŸ‘·Contract-to-hire trials
    • πŸ›«Onboarding
    • πŸ†IC Levels
    • πŸ’‘Sharing your views
    • πŸ’ΈBonus & Equity Structure
  • Policies
    • πŸ–οΈVacations
    • πŸ’³Expenses
    • πŸ—£οΈCommunications
  • Engineering
    • πŸ””Managing Notifications
    • ⭐Valuable Bookmarks
    • πŸ›How to report issues
    • πŸ’»How we work on Tickets
    • πŸ”₯What to do during Emergencies
    • βœ…PR Reviews
    • β˜‘οΈSelf-reviews
    • πŸ“šKeeping Docs up-to-date
    • 🌐HTTPS & Subdomains
    • 🎯Best practices
    • πŸ’»Codebase
      • πŸ”“Keeping the lock file in sync
      • 🚫Git Private Submodules
      • 🏎️Monorepo / Turborepo
      • 🌝Deploying to Production
      • ☁️Deployment
      • πŸ’»Debug Desktop App
      • 🚩Enabling/Disabling Features
    • πŸ”ΊResolving failed migration on Vercel Preview
    • πŸ”¦Cal.com Status Page
  • Customer Success
    • πŸ’ŸTone
  • Marketing
    • 🎬Media
    • ☝️How to add a new Tip to Sidebar
  • 🀲Sales
    • Operations Stack
Powered by GitBook
On this page

Was this helpful?

  1. Engineering

πŸ’»Codebase

Specific tactical knowledge about how we organise, deploy and work with code at cal.com

πŸ”“Keeping the lock file in sync🚫Git Private Submodules🏎️Monorepo / Turborepo🌝Deploying to Production☁️DeploymentπŸ’»Debug Desktop App🚩Enabling/Disabling Features
PreviousE2E Tests Best PracticesNextKeeping the lock file in sync

Last updated 1 year ago

Was this helpful?