Welcome aboard! 👋

📬 Before Day 1

You should have received an email from IT with a link to activate your Google Workspace account (yourname@pipeshub.com). Do this before day 1 — everything else depends on it.

🔑 Day 1 — Accounts & Access

Work through this list in order. Click items to mark them done.

Automatic on Google activation

1. Gmail, Google Calendar, Google DriveAuto
2. Notion (company workspace) — sign in with Google at notion.soAuto
3. Linear (issue tracker) — sign in with Google at linear.appAuto
4. Loom — sign in with GoogleAuto

Request from your manager

1. AWS console access — send your IAM username request to #eng-opsAsk @rahul
2. GitHub org membership (github.com/pipeshub) — ask @rahul to invite your handleAsk @rahul
3. 1Password Teams — invite email will arrive once addedAsk @rahul

Set up yourself

1. Slack — download the desktop app, sign in to pipeshub.slack.comSelf
2. Join channels: #engineering, #backend, #deployments, #incidents, #general, #randomSelf

💻 Day 2 — Dev Environment

Prerequisites

Confirm these are installed before cloning:

• Node.js 20+ — node --version
• Python 3.12+ — python3 --version
• Docker Desktop (must be running)
• git configured with your @pipeshub.com email

Setup steps

1. Clone the repository

   bashCopy

   git clone git@github.com:pipeshub/pipeshub-ai.git
   cd pipeshub-ai
   cp .env.example .env.local

   Fill in .env.local from the values pinned in #eng-onboarding. Don't commit it.

2. Install dependencies

   bashCopy

   # Node / TypeScript
   npm install
   
   # Python service layer
   pip install -r services/requirements.txt --break-system-packages

3. Start all services

   bashCopy

   docker compose up -d
   npm run dev
   
   # In a second terminal:
   cd services && uvicorn main:app --reload

   App at http://localhost:3000 · API at http://localhost:8000

4. Run the test suites — all should pass on a clean checkout

   bashCopy

   npm test                   # TypeScript unit tests
   cd services && pytest       # Python tests
   npm run test:integration    # Requires Docker

📅 How We Work

Meeting rhythm

Pull request rules

• Branch naming: your-name/short-description (e.g., arjun/fix-s3-content-type)
• PR must have a description, Linear issue link, and at least one test change
• Request review from ≥1 person; ≥2 for anything touching auth or credentials
• Squash-merge to main
• CI must be green before merging — no exceptions

🗂️ Codebase Orientation

Start reading: src/webhooks/router.ts → services/agents/base_agent.py → services/connectors/

👥 Who to Ask About What

When in doubt, ask in #engineering — someone will route you to the right person.