Pr Iteration

Iteration Workflow

Phase 1: Pre-Flight Checks (Before Creating PR)

# 1. Install dependencies
bun install

# 2. Run linting
bun run lint

# 3. Run type checking
bun run typecheck

# 4. Run tests
bun run test

# 5. Run build
bun run build

If any check fails → FIX IT before proceeding

Phase 2: PR Creation & Initial Validation

After creating PR/MR:

# 1. Verify all checks pass locally
bun run lint && bun run typecheck && bun run test && bun run build

# 2. Push and wait for CI

# 3. Monitor CI results

Phase 3: Iterative Fix Loop

While any check is failing:

CHECK → FAIL → FIX → COMMIT → PUSH → RE-CHECK → (REPEAT UNTIL PASS)

Priority order for fixing failures:

1. Linting errors (formatting, style) - Usually quickest to fix
2. Type errors - May require interface changes
3. Test failures - Logic bugs or test updates needed
4. Build failures - Often the most complex

Phase 4: Final Verification

# Run full check suite one more time
bun run lint
bun run typecheck
bun run test
bun run build

Only declare PR ready when ALL checks pass.

Common Failure Patterns & Fixes

Pattern 1: Linting Failures

Symptom: CI fails on bun run lint or biome/eslint errors

Fix Process:

# Run auto-fix first
bun run lint --fix
# or
biome check --write .

# If manual fixes needed, address each error
# Re-run lint to verify
bun run lint

Iterate until: bun run lint exits 0

Pattern 2: Type Errors

Symptom: bun run typecheck or tsc fails

Fix Process:

# Run type check
bun run typecheck

# Fix each error:
# - Add missing types
# - Fix interface mismatches
# - Update imports

# Re-run typecheck
bun run typecheck

Iterate until: bun run typecheck exits 0

Pattern 3: Test Failures

Symptom: Tests fail locally or in CI

Fix Process:

# Run failing test
bun test path/to/failing-test.ts

# Debug and fix
# - Check test expectations
# - Verify mock setup
# - Review logic changes

# Re-run test
bun test path/to/failing-test.ts

# Run full test suite
bun run test

Iterate until: All tests pass

Pattern 4: Build Failures

Symptom: bun run build or nx build fails

Fix Process:

# Run build with verbose output
bunx nx run-many --target=build --all --verbose

# Identify failing package
# Check error message

# Common causes:
# - Missing dependencies in package.json
# - Import errors
# - TypeScript compilation errors

# Fix issue
# Re-run build
bun run build

Iterate until: Build succeeds

Pattern 5: Cross-Package Failures

Symptom: Changes in one package break another

Fix Process:

# Identify affected packages
bunx nx affected:graph

# Build dependency graph first
bunx nx run-many --target=build --projects=dependency-package

# Then build dependent
bunx nx run-many --target=build --projects=dependent-package

# Run tests on affected packages
bunx nx affected:test

Iterate until: All affected packages build and test successfully

CI/CD Integration

GitHub Actions Workflow