Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.thesozocrm.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Team Development Workflow

Our team uses a modern, async-first workflow centered around Linear for issue tracking and GitHub for code collaboration.

​
Linear Workflow (Issue Tracking)

​
Overview

Linear is our single source of truth for:
  • 🐛 Bug reports
  • ✨ Feature requests
  • 📋 Task tracking
  • 🏃 Sprint planning
  • 📊 Progress monitoring

​
Linear Setup (10 minutes)

1

Accept Invitation

Check your email for Linear workspace invitation to “Elevate CRM”
2

Create Account

Use the invitation link from your email to join the Linear workspace
3

Install Desktop App (Optional)

Download Linear desktop app for faster access (optional)
4

Enable Notifications

Go to Settings → Notifications and enable:
  • Email notifications for mentions
  • Desktop notifications for assigned issues
5

Connect GitHub

Linear will auto-connect to GitHub and link PRs to issues

​
Linear Structure

​
Teams

  • Engineering: All developers (you’re here!)

​
Projects

Core Features

Major features and enhancements

Bug Fixes

Bug reports and fixes

Technical Debt

Refactoring and code improvements

Documentation

Documentation updates

​
Labels

  • good-first-issue - Perfect for new developers
  • bug - Something isn’t working
  • feature - New functionality
  • enhancement - Improvement to existing feature
  • urgent - Needs immediate attention
  • blocked - Waiting on external dependency

​
Priorities

  • 🔴 Urgent: Drop everything
  • 🟠 High: This sprint
  • 🟡 Medium: Next sprint
  • 🟢 Low: Backlog

​
Daily Workflow with Linear

​
1. Start Your Day

1

Open Linear

Open Linear (use the link from your invitation email)
2

Check Your Issues

Click “My Issues” to see what’s assigned to you
3

Check Current Sprint

View the active cycle to see team progress
4

Pick Next Task

Move an issue from “Todo” to “In Progress”

​
2. Working on an Issue

Create Branch
# Use Linear issue ID in branch name
git checkout -b feature/ELE-123-add-copy-button

# Linear auto-detects the issue from your branch name!
Pro Tip: Always include the Linear issue ID (e.g., ELE-123) in your branch name and commit messages. Linear will automatically link everything!

​
3. Creating a Pull Request

When you create a PR on GitHub:
1

Reference Linear Issue

Include Linear ID in PR title:
Add copy button for deal IDs (ELE-123)
2

Auto-Link

Linear automatically detects and links the PR to the issue
3

Update Status

Move Linear issue to “In Review”
4

After Merge

Linear auto-moves issue to “Done” when PR is merged!

​
4. End Your Day

  • Update progress on Linear issues
  • Add comments for anything blocking you
  • Set status for tomorrow’s work

​
Git Flow Workflow

We use a simplified Git Flow model:

​
Branch Structure

main (production)
  ↑
dev (integration)
  ↑
feature/ELE-123-my-feature (your work)

​
Creating Feature Branches

Feature Branch Workflow
# 1. Start from dev branch
git checkout dev
git pull origin dev

# 2. Create feature branch (include Linear ID!)
git checkout -b feature/ELE-123-add-dashboard-widget

# 3. Work on your feature
# ... make changes ...

# 4. Commit frequently (include Linear ID)
git add .
git commit -m "feat: add dashboard widget (ELE-123)

- Add widget component
- Connect to Redux store
- Add loading states"

# 5. Push to GitHub
git push origin feature/ELE-123-add-dashboard-widget

# 6. Create Pull Request on GitHub
# Linear will auto-link it!

​
Branch Naming Convention

TypeExampleWhen to Use
feature/ELE-123-*feature/ELE-123-user-searchNew features
fix/ELE-123-*fix/ELE-123-login-bugBug fixes
refactor/ELE-123-*refactor/ELE-123-api-cleanupCode refactoring
docs/ELE-123-*docs/ELE-123-api-guideDocumentation
test/ELE-123-*test/ELE-123-unit-testsTest additions

​
Commit Message Format

​
Standard Format

type: short description (ELE-123)

- Bullet point details
- What changed
- Why it changed

Related: ELE-456

​
Commit Types

  • feat: New feature
  • fix: Bug fix
  • refactor: Code refactoring
  • docs: Documentation
  • test: Test additions
  • chore: Maintenance tasks
  • perf: Performance improvements

​
Examples

feat: add copy button to deal cards (ELE-123)

- Add clipboard icon button to DealCard component
- Show toast notification on successful copy
- Add keyboard shortcut (Cmd+C)

Improves UX by allowing quick deal ID copying

​
Pull Request Process

​
1. Create PR

1

Push Branch

git push origin feature/ELE-123-my-feature
2

Open GitHub

GitHub will show “Compare & pull request” button
3

Fill Template

Use the PR template (auto-filled):
  • Summary of changes
  • Linear issue link
  • Testing steps
  • Screenshots (if UI changes)
4

Request Review

Request review from @chandlerking or senior dev

​
2. Code Review

As Author:
  • Respond to feedback within 24 hours
  • Make requested changes
  • Re-request review after changes
As Reviewer:
  • Review within 48 hours
  • Be constructive and specific
  • Approve when ready or request changes

​
3. Merge

1

All Checks Pass

Ensure all CI checks are green
2

Approved

Get approval from reviewer
3

Squash and Merge

Use “Squash and merge” button
4

Delete Branch

GitHub will prompt to delete the branch - do it!
5

Linear Auto-Updates

Linear automatically moves issue to “Done” 🎉

​
Sprint Workflow (2-Week Cycles)

​
Sprint Planning (Monday Week 1)

1

Review Backlog

Team reviews Linear backlog together
2

Estimate Issues

Add time estimates to issues:
  • Small: 1-2 hours
  • Medium: 4-8 hours
  • Large: 16+ hours (break into smaller issues)
3

Assign to Cycle

Move issues to current cycle in Linear
4

Assign to Developers

Each dev gets assigned their issues

​
During Sprint

  • Check Linear daily
  • Update issue status as you work
  • Comment on blockers immediately
  • Move completed issues to “Done”

​
Sprint Review (Friday Week 2)

  • Demo completed features
  • Update Linear issue statuses
  • Move incomplete issues to next sprint

​
Communication Guidelines

​
When to Use Email

Email chandlerking@elevateyouenterprise.com

  • Urgent production issues
  • Questions about architecture decisions
  • Onboarding questions
  • Time off requests

​
When to Use Linear

Use Linear for

  • Bug reports
  • Feature requests
  • Task updates
  • Technical discussions on specific issues
  • Questions about implementation

​
When to Use GitHub

Use GitHub PRs for

  • Code reviews
  • Technical implementation discussions
  • Suggesting code changes

​
Keyboard Shortcuts

​
Linear Shortcuts

ShortcutAction
CCreate new issue
QQuick find
/Search
IAssign to me
SChange status
LChange label
PChange priority

​
GitHub Shortcuts

ShortcutAction
TFile finder
BBlame view
/Search
G then IGo to issues
G then PGo to pull requests

​
Best Practices

​
Linear Best Practices

❌ Bad: “Button doesn’t work”✅ Good: “Save button on deal edit page returns 403 error”
Include:
  • Steps to reproduce (for bugs)
  • Expected vs actual behavior
  • Screenshots/videos
  • Browser/environment info
  • Update status as you work
  • Comment on progress
  • Add blockers immediately
Always add appropriate labels:
  • Issue type (bug, feature, etc.)
  • Priority
  • Difficulty (for new devs)

​
Git Best Practices

  • Commit every logical change
  • Don’t wait until end of day
  • Easier to review and revert
  • Use present tense (“Add” not “Added”)
  • Be specific about what changed
  • Include the “why” not just “what”
  • Target: < 400 lines changed
  • One feature/fix per PR
  • Easier and faster to review
Before requesting review:
  • Read through your own changes
  • Test thoroughly
  • Check for console.logs
  • Run linter

​
Common Workflows

​
Workflow: Report a Bug

1

Open Linear

Go to Linear workspace
2

Create Issue

Press C or click “New Issue”
3

Fill Details

  • Title: Clear description
  • Description: Steps to reproduce
  • Label: bug
  • Priority: Set appropriately
  • Screenshots: Attach if helpful
4

Submit

Issue is created and team is notified

​
Workflow: Request a Feature

1

Create Linear Issue

New issue with feature label
2

Describe

  • What problem does it solve?
  • Who benefits?
  • Mockups/examples if helpful
3

Team Reviews

Team discusses in Linear comments
4

Gets Prioritized

Added to backlog or upcoming sprint

​
Workflow: Fix a Bug

1

Find Issue in Linear

Look for bug label issues
2

Assign to Self

Click “Assign to me”
3

Move to In Progress

Update status
4

Create Branch

git checkout -b fix/ELE-123-button-bug
5

Fix & Test

Make changes and test thoroughly
6

Commit & Push

git commit -m "fix: resolve save button error (ELE-123)"
git push origin fix/ELE-123-button-bug
7

Create PR

Reference Linear issue in PR
8

Move to In Review

Update Linear status
9

After Merge

Linear auto-completes! 🎉

​
Quick Reference

​
Linear States

  • Backlog: Not yet planned
  • Todo: Planned for current sprint
  • In Progress: Actively working on it
  • In Review: PR is open
  • Done: Merged and complete
  • Cancelled: Won’t do

​
When to Update Status

  • Start working → In Progress
  • Open PR → In Review
  • PR merged → Done (automatic!)
  • Can’t complete → Cancelled

​
Need Help?

Linear Help Docs

Official Linear documentation

Email Support

chandlerking@elevateyouenterprise.com
Last Updated: November 4, 2025